autopilot

# Autopilot Drive a single GitHub issue through the project's full development loop with minimal supervision, stopping at a boundary you authorize up front. This composes the existing skills (`/resolve-issue`, `/simplify`, `/create-pr`, `/verify`, `/walkthrough`, `/code-review`) plus `bin/ci` — it does not reinvent them. Use this when an issue is clear and well-specified and you want it carried to a review-ready PR (or, for small reversible changes, all the way to merge) without invoking each step by hand. For issues that need close collaboration, use the individual skills instead. ## Arguments `$ARGUMENTS` contains the issue number and an optional tier flag: - **`--to pr`** (default): run the full loop and **stop at a review-ready PR**. No merge, no deploy. This is the well-lit path — the human merge gate catches everything. - **`--to merge`**: run the full loop, then merge (which auto-deploys) **only if the change passes the narrow-class gate** in Step 8. Otherwise it degrades to `--to pr` and stops. Passing `--to merge` IS your per-run authorization to merge this one issue; it is not a standing capability. Examples: `/autopilot 754` (→ pr), `/autopilot 754 --to pr`, `/autopilot 847 --to merge`. Parse the issue number and tier from `$ARGUMENTS`. If no tier is given, default to `pr`. If the tier is unrecognized, stop and ask. ## Build model — reconcile against the issue's `model:` label Repos that have adopted the per-issue model convention (`~/.claude/docs/model-se...