shiplisted

# /ship — pre-PR checklist You are about to open a pull request. Run this checklist **in order**. Stop and report failure at the first red step — do not proceed past a failure without explicit confirmation from the user. ## 1. Verify worktree ```bash git rev-parse --abbrev-ref HEAD git status --porcelain git rev-parse --show-toplevel pwd ``` Confirm: am I on the intended branch, in the intended worktree, with the intended changes staged? If anything looks off (wrong worktree, branch named after a different feature, surprise files), stop and ask. ## 2. Run the test suite Use the project's test command. Read `package.json`, `pyproject.toml`, `Makefile`, or CLAUDE.md to find it. Common patterns: - `npm test`, `pnpm test`, `yarn test` - `uv run pytest`, `pytest` - `flutter test` - `go test ./...` - `cargo test` Report the result explicitly. If tests fail, fix them. Do not skip. ## 3. Run lint If the project has a linter (biome, eslint, ruff, prettier, dart format, gofmt, etc.), run it. Auto-fix what you can. Report unresolvable warnings. ## 4. Run typecheck / static analysis - `npm run typecheck`, `tsc --noEmit` - `astro check` - `flutter analyze` - `mypy`, `pyright` - `go vet`, `cargo clippy` Stop on errors. ## 5. Re-read the spec If this branch has a corresponding spec (`docs/spec.md`, a GitHub issue, a design doc, a `.claude/plans/*.md`), re-read it now. Compare what shipped to what was specified. List any gaps explicitly. **For each gap, either fix it now or fi