dotfiles

Create a pull request with auto-generated description, issue linking, ROADMAP updates, and PR-metadata validation.

Merge a pull request with status checks, squash merge, and branch cleanup. Handles worktree contexts.

Fan out a batch of autopilot-queued issues to parallel background worktree subagents — each runs /autopilot — with an Opus gating review on every Sonnet-built PR.

Detailed technical walkthrough covering architecture, test coverage, product tour, and key design decisions.

Pre-PR advisory check for deviations from the project spec. Read-only analysis.

Generate a hands-on QA testing guide as a self-contained HTML page — for Rails apps or static (Hugo) sites. --publish uploads the HTML to the project's configured QA host.

Triage a QA-labeled report — investigate it against the code, classify it, and draft the technical issue(s) it warrants, stopping for approval before creating anything.

Fan out /qa-triage across a queue of qa-labeled reports in parallel, reconcile them across reports to cluster shared root causes, present one consolidated decision gate, and — on approval — create the resulting tech issues.

Vet open issues for autonomous resolution and queue the qualifying ones with the autopilot-queued label — the start-of-day "fill the queue" half of the triage → run split.

Carry a well-scoped GitHub issue through the full dev loop autonomously, stopping at a per-run tier boundary (PR-ready, or merge+deploy for small reversible changes).

Full issue workflow — fetch details, research, plan solution, implement, and verify.

Generate a hands-on browser walkthrough of a PR's user-facing changes to exercise before review; --publish posts the final version to the PR for QA.

Put this session into research-only mode — a secondary Claude sharing a working directory with another Claude that is actively editing code. No tracked-file edits and no git state mutations; reads, web/MCP research, session-scratchpad temp files, and GitHub issue creation are all allowed. Use at the start of a parallel planning/research/drafting session.

Set up PRD-driven development infrastructure for a new project, including directory structure, templates, and roadmap.

Assess a project that's been dormant for months and produce a prioritized re-entry plan — lifecycle stage, what's stale or broken, and how far the project's tooling has drifted from current conventions — delegating every fix to the skill that owns it, and optionally capturing the plan as a tracking issue that survives sessions.

Render a PRD Markdown file as a rich, self-contained HTML reading view (Dashboard style) and open it in the browser. The Markdown stays authoritative; the HTML is a derived, ephemeral presentation.

Dependabot-aware dependency updates with security audit, real-CI validation, and a unified PR. Framework-agnostic.

Manage Todoist tasks, projects, labels, filters, sections, comments, reminders, and workspaces via the `td` CLI. Use when the user wants to view, create, update, complete, or organize Todoist items, or mentions tasks, inbox, today, upcoming, projects, labels, or filters.

Audit and update a project README, or bootstrap a new one. Detects tech stack, versions, and services.

Quick 2-minute status update on current phase, completed work, blockers, and health check.

Convert a Markdown file to PDF with GitHub-style formatting using the md2pdf tool.

Plan the next PRD phase by drafting issues, creating GitHub issues, and bridging planning to building.