skill
Final mile from merge-ready branch to shipped: squash-merge, archive backlog tickets with trailers, update touched docs, run /reflect, apply outputs. Assumes /deliver or /deliver --polish-only already made the branch ready. Use when: "ship it", "merge and close out", "final mile", "land and reflect", "finish this ticket". Trigger: /ship.
/ship
Source: skills/ship/SKILL.md
Final mile from merge-ready branch to shipped: squash-merge, archive backlog tickets with trailers, update touched docs, run /reflect, apply outputs. Assumes /deliver or /deliver --polish-only already made the branch ready. Use when: "ship it", "merge and close out", "final mile", "land and reflect", "finish this ticket". Trigger: /ship.
Ship primitive in the Harness Kit operating loop.
This generated excerpt gives readers the beginning of the live primitive contract before they jump to GitHub.
The final mile. Branch is merge-ready; `/ship` lands it, archives the
ticket(s), syncs docs, runs `/reflect`, and threads reflect's outputs back
into the repo. One command from "green" to "shipped and learned from."
## Stance
1. **Act, do not propose.** `/ship` has authority within its domain.
Archive, merge, pull, reflect, apply. Escalate only on refuse conditions.
2. **Never lose trailer context.** `Closes-backlog` trailers must survive
into the squash commit on master. `/groom` sweeps master by trailer —
a dropped trailer is a ticket that never closes.
3. **Pre-merge prep belongs on the shipping branch.** Archive moves and
doc syncs go on the feature branch before the squash so the merge
commit itself carries a single, clean closure event.
4. **Reflect's harness edits never touch master.** They land on a
`harness/reflect-outputs` branch for human review. This is a hard
invariant from `reflect/SKILL.md`.
5. **Not a CI runner, not a reviewer, not a refactorer.** `/ship` assumes
`/deliver --polish-only` already proved the branch clean. If it wasn't
run, refuse and route the operator back.
6. **Roster receipts are required evidence.** In repos with
`.harness-kit/agents.yaml`, verify that `/deliver --polish-only` or the
documented landability evidence includes two or more roster-member receipts
or an explicit exception before final-mile merge work.
## Delegation Floor
Delegation floor applies: probe the roster first; dispatch two or more
providers for substantive work; direct solo only for mechanical, emergency,
user-forbidden, or fewer-than-two-providers cases. See
`harnesses/shared/AGENTS.md` (Roster).
Local lane guidance: Normally verify upstream roster receipts; if final-mile work surfaces substantive judgment, route back to /deliver --polish-only or dispatch release-risk and closure-state review lanes.
...