ship-it

# Ship It Open or update a PR for the current work. Quality is enforced locally, BEFORE the PR exists — cloud auto-review is disabled by design. Do not re-enable it, request bot reviews, or wait for them. 1. Read the repository instructions and inspect the current branch, diff, and working tree. Preserve unrelated user changes. Before review, mark each intended untracked path with `git add --intent-to-add -- <path>` so the complete diff includes its contents; never do this to unrelated files. 2. **Local dual-review gate** (skip only for diffs touching exclusively docs/markdown/config with no runtime surface). This is a fresh adversarial review of the FINAL diff — reviews that happened while writing the code (pair acceptance, impeccable, in-flight feedback) are a different thing and leave this gate unrun: - Run your own NATIVE review harness against the merge base with the target branch. Use each agent's native command surface, not an assumed repository skill: - Claude Code: run its native local-worktree `/code-review` command on Opus. The headless form is `claude -p --model opus --permission-mode plan --output-format text "/code-review"`. This is a Claude command, not a repository skill. - Codex: run `codex review "<final-diff review prompt>"`. Do not use `--base` when the final diff also has staged or unstaged changes because that mode omits them; do not use generic `codex exec` for this gate. ...