ship

Ship

/ship closes completed code work through a pull request. Knowledge-note lifecycle and external publication remain host concerns. You already know how to write a commit; this skill is the gate sequence, not the coaching.

Gates (in order, none skippable silently)

1. Config — read the ## verbs block from CLAUDE.md or AGENTS.md for the test command, tag format, and release preference.
2. Pre-flight — git pull; run the project's test/build command and STOP on failure with the output; inspect git diff --stat, git log origin/{main}..HEAD --oneline, and the current branch.
3. Pitfall ack — search {learnings_dir} for type: pitfall entries whose files: touch changed files; a match must be listed and acknowledged before proceeding. Skip only what an earlier read this session already listed by this same query: an escalated review's RECALL block covers an entry only when it actually named it. Running review is not itself evidence — its recall ranks by topic-token overlap against title and tags, takes the top 3-5, and drops effective confidence below 3, so a pitfall naming a changed file can sit outside its results entirely. Same store, different query. Acknowledge the remainder here.
4. Scope check — if a brief for this branch exists in docs/briefs/, compare the current full diff against its Scope In/Out and the diff at review time. Print Scope: ON TRACK, or SCOPE DRIFT: [...] / POST-REVIEW CHANGES: [...] and ask before proceeding. No brief → still warn on commits made after the last /review this session.
5. Review gate — if /review has not run on the current diff this session, warn: "Review not run. Run /review first?" Proceed only on an explicit skip.
6. Branch before commit (hard rule) — never push to main/master; always ship via PR. On main → create fix/* / feat/* / refactor/* BEFORE staging; a branch created after the commit still advances the local default branch.
7. Commit — stage relevant files only (never git add -A); conventional message type(scope): description; empty git diff --cached after staging → report and skip the commit; never amend, never skip hooks.
8. Tag / release (config-gated) — tag: semver → derive the bump from commits (feat = minor, fix = patch) and tag; release: true → GitHub Release from the tag with generated notes. Truth gate before publishing: every PR / SHA the notes cite must be an ancestor of the tag (git merge-base --is-ancestor), and added/removed claims must match git diff {prev-tag}..{tag} --stat — the notes describe what the tag contains, nothing more. On mismatch fix the notes, never re-tag. Otherwise skip both.
9. Push + PR — push with -u (plus tags if created); gh pr create with a title under 70 chars and a what/why/how-to-test body. Resolve an existing PR instead of creating a duplicate.
10. QA evidence upsert — when qa ran, read the handoff from the Git metadata path defined in lib/qa-evidence-format.md. Recompute its artifact identity against the PR head, then create or update the authenticated viewer's single marker comment. Read the comment back before reporting its URL. A stale artifact, malformed block, FAIL, or UNPROVEN row still gets published as Acceptance: NOT VERIFIED, but blocks a ready/done claim. For a UI diff that required qa, missing evidence also blocks completion. For non-UI work, state QA evidence: not applicable; never fabricate a report. Re-running ship updates the same comment rather than adding another.
11. Artifact proof — before asking a human to validate an artifact or using manual validation as completion evidence, apply lib/verify-the-test-loop.md and prove that the tested artifact contains the current commit. Missing artifact identity blocks the completion claim.
12. Closure evidence — done means the PR URL, pushed commit/branch, and, when QA ran, the verified QA comment URL are printed. Missing delivery evidence → name the gap and do not claim done.