Workflow · ShipDraft
Commit to merged, in one pass. Not done until it is merged and green.
Every check that only needs your working tree fires at once. The pull request is then driven through CI, fix rounds and the merge queue, with every wait bounded. An open pull request is an unfinished ship.
/shipShips the current worktree’s branch. By default the heavy checks run in CI against a draft pull request; --local runs everything on your machine.Open source, free: skills/ship/SKILL.md. The step numbers below match the file.
Step by step
- −1
Model checkYou decide
If you have set a model for shipping and the session is on a different one, it asks once: continue, or stop so you can switch. On stop, nothing has been touched.
- 0
Pre-flightBlocking gate
Three blocking checks before anything runs.
- Branch sanity: not a protected branch, not detached, and it has something of its own to ship
- Protected files: a change to a file you have marked protected stops the ship until you approve it, and the approval is logged in the pull request
- Base-branch health: if the base branch is already red, stop
- 0.7
Sync firstBlocking gate
The branch is rebased onto the base branch before any check fires. Every check then runs against the code that will actually merge.
- 1
Fire everything
In one turn: typecheck, lint, tests, build, scans, the documentation update and the search for related tickets. If a valid record exists for this exact code from an earlier run, the heavy tasks are not repeated.
- 2
Collect and triageBlocking gate
A red check blocks the ship. That includes failures that were there before and failures outside this diff. Attribution decides where the fix lands, never whether to fix. The pull request title and body are drafted from what was actually done.
- 3
Commit and push
After the documentation step has finished, so the docs ride in the same commit.
- 4
Open the pull request
A draft by default. The end-to-end gate is checked against the record that code review wrote for this exact code.
- 4.5
Watch CI, fix, flip to readyBlocking gate
Every failed job is read before any file is touched. The union is fixed and pushed once. Fix rounds are capped. A red draft never flips to ready and never enters the queue. There is no waiver.
- 5
Merge, post-merge, close out
The pull request is enqueued or merged. The skill then watches post-merge CI, closes the tickets it covered, moves them to done and cleans up the worktree. Only then does it report done.
Why it is shaped this way
Scripts hold the gates
Fingerprints, bounded waits, the failure census and the round cap are scripts with exit codes. The model does the judgment; it does not re-derive a gate under pressure.
Offload is not skip
When heavy checks move to CI they still run and still block. Skipping a check with no CI job behind it is a bug.
Every wait is bounded
An unbounded watch on a stuck job hangs a session for hours. Each wait has a limit and a defined next step when it is reached.
One push per census
Read every failure, fix them together, push once. Fixing one failure per CI round rediscovers the same problems three times.
It asks you very little
There is a short written list of question types the skill may ask. Everything else follows a rule, is logged as an automatic decision, and keeps going.
What it will not do
- Ship with a red check, including one it believes is unrelated.
- Say done while the pull request is still open.
- Accept a review record written for different code.
Questions
Why does it ask about the model?
Shipping is procedural work that a cheaper model does well. The check lets you switch before any state is touched, and a compact first keeps the ship session small.
What if I have no merge queue?
It merges directly. Queue, labels and board moves are configuration slots; unset ones are skipped and reported.
What happens after a restart or a compaction?
The skill keeps its state on disk and opens with a resume section. It reads where it was and continues from that step.