shiplisted

# Ship — working tree to green PR, one command Orchestrate the existing skills in order. **Invoke each stage via the Skill tool — never re-implement a stage's logic inline.** This skill only owns sequencing, gates, state, and the final report. ## Flags (parse from $ARGUMENTS) | Flag | Effect | |------|--------| | `--fast` | Skip Stage 1 (simplify) and Stage 3 (code-review) — for tiny changes | | `--merge` | Squash-merge once green (default: stop at green, human merges) | | `--effort low\|medium\|high` | Pass through to code-review (default: medium) | | `--no-verify` | Skip Stage 2b (runtime verify) — docs/config-only changes. The Stage 2a rebase check still runs | ## Cross-cutting rules - **Fail loud, never skip silently.** A stage that fails HALTS the pipeline with the evidence. A stage skipped by flag must be named as "skipped (--flag)" in the final summary. Never report "shipped" if anything was silently skipped. - **Project CLAUDE.md overrides this recipe.** Examples: a project may forbid a tracked CHANGELOG.md (skip smart-commit's changelog step there); a project may require tests to run on a remote host instead of locally; a project-specific verify/test recipe always beats the generic one. - **State file** `.claude/ship-state.json` (repo-local): write `{branch, head_sha, flags, completed_stages: []}` after each stage; on invocation, if it exists and `branch` matches the current branch, offer to resume from the next stage; delete it on success. ## Stage 0 — Preflig