joshukraine/dotfiles

resolve-issue

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

autopilot-batch

Fan out a batch of autopilot-queued issues to parallel background worktree subagents — each runs /autopilot at the build model from its 'model:' label — with a gating review at Opus 5 or above and never below the build (Opus reviews Sonnet and Opus builds,…

autopilot

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).

model-triage

Adopt the per-issue model-selection convention in a repo — tier every open issue, apply the model: labels, board field, and callouts behind an approval gate. Also runs in maintenance mode to sweep up unlabeled issues and label/field drift.

qa-triage-batch

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.

autopilot-triage

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.

ruby-gc

Audit asdf-installed Ruby versions against project pins and remove unreferenced ones. Dry-run by default.

create-pr

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

merge-pr

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

debrief

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

drift-check

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

qa-handoff

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.

qa-triage

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.

walkthrough

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.

sidecar

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…

bootstrap-prd

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

dustoff

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…

prd-view

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.

update-deps

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

todoist-cli

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,…

readme-refresh

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

checkpoint

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

md2pdf

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

plan-phase

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