Done

Ship the current branch — by updating an existing PR, merging locally to main, or creating a PR when main is protected.

The deterministic plumbing (PR check → protected check → fast-forward merge → push) lives in scripts/ship.sh so the common local-merge path runs in one shot instead of many model round-trips. Deciding what to ship is judgment, so the script never stages or commits — you commit deliberately, it requires a clean committed tree, then it merges and pushes. The script auto-completes only the well-understood happy path; for anything unusual it prints a HANDOFF (with full state already gathered) and you take over.

Workflow

0. Pre-flight — verify repo requirements

Find and read whichever convention/instruction files apply to this repo and harness (e.g. AGENTS.md, CLAUDE.md, CONTRIBUTING.md, .cursor/rules/*, .github/copilot-instructions.md, .clinerules, etc. — follow any @-includes). Verify the branch satisfies the rules; fix or surface gaps before continuing. If a repo mandates a check before shipping (e.g. just ci), run it now.

1. Review and commit

Look at git status / the diff and confirm the working tree contains only the change you intend to ship — watch for unrelated edits or stray/untracked files. Stage deliberately (git add -A only once you've confirmed the tree is clean of anything that shouldn't ship; otherwise stage specific paths), then commit with a crafted message. Leave the working tree clean.

2. Run the ship script

From inside the branch's worktree: