ship-itlisted

# Ship It Open or update a PR for the current work. Quality is enforced locally, before the PR exists. Run it only when the user invokes ship-it or another skill (an orchestrator's graded gate) delegates to it — finishing a change is not an invitation to ship it. 1. Read the repository instructions and inspect the current branch, diff, and working tree. Preserve unrelated user changes. `git fetch origin <target-branch>` first, and take every merge base in this skill against `origin/<target-branch>` — a stale local target reviews another PR's commits. 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. **Grade the gate.** A reproduced, localized, reversible production hotfix with a focused regression and no migration, auth or permission, payment, destructive-infrastructure, or public-API change uses `single`: skip pool grading and run only the current agent's native review. Otherwise the gate spends both usage pools — Claude (simplify + review) and Codex (review) — so fix its level before anything runs. When an orchestrator names a graded gate, ship-it still owns this hotfix check: `single` overrides that grade; otherwise the orchestrator's grade wins. Read the pools either way: run `node scripts/usage-state.mjs` from the herdr-orchestrate skill installed alongside this one; a pool is out of headroom at `used_