matthewwong525/WongStack / .agents/plugins/loop/skills/ship
ship
Verified/ship
Invoking /ship authorizes every step below unprompted: archive, checkpoint, walk, merge, remote-branch deletion, sync, the pull-in with any save a task needs, and safe picks. Confirm anything else (a force push, --no-verify, git reset --hard, checkout .) in the shared ask format.
The loop's rules own the record and the gate. main means the default branch.
Each command ends with a NEXT: line; follow it:
SHIP="$(git rev-parse --show-toplevel)/.claude/skills/ship/scripts/ship.mjs"
node "$SHIP" prepare --change "$CHANGE_NAME"
node "$SHIP" finish
Step 1 — preflight
Attached review notes → apply them to the existing change first, then keep publishing.
Check preconditions, then run prepare. Uncommitted changes on the default branch stay put; Step 3's save cuts the feature branch.
The pull-in: nothing to ship yet
Invoke the apply skill, saying it runs inside /ship, then go to Step 2 in the same tree.
/ship <intent>→ pass the intent verbatim.- No argument → invoke
/applybare when its resolve order lands beforesole-active, or the session states clear intent with no change yet. - The cold stop. Landing on
sole-activeor nothing → say there is nothing to continue and/ship <intent>starts a new change, then stop: a cold/shipnever publishes the only open plan.
/plan pauses, tasks stay pending, or a task-driven /save fails or is unverifiable → report the blocker and stop before Step 2: no verb merges to stop.
Work that changes no repo file finishes in /apply: say so in one line and stop.
Step 2 — archive the change
Run node .claude/plugins/loop/scripts/slot.mjs stepTitle set SHIP --task "<plan title>", again after each apply until finish merges, then set DONE. Pass --change for a change the person or this chat named; without it prepare picks by the rungs. None selects → follow NEXT:; a new change comes from the new-plan fallback.
prepare archives by the CLI contract, which owns --skip-specs, after two stops:
- Other changes the branch adds → rerun with
--move-others;--allow-othersonly if the person asked to ship all. - Unchecked tasks → invoke
applyfor that change inside/ship, then rerun; still pending → report and stop.
Step 3 — delegate the checkpoint to /save
prepare numbers the ## Next changelog entry, merging main first when behind, then reruns the local checks: allow 15 minutes. /save packs ARCHIVE; archive.mjs unpack <name> --edit reopens it.
Invoke the save skill once (plus one after Step 4's fix) as ordinary /save inside /ship and follow it verbatim, with prepare's CHANGE and ARCHIVE if any. Proceed only on SUCCESS, NONE, or LOCAL. Any other result → stop before merge and report /save's reason; never repeat, bypass, or reinterpret the gate.
Step 4 — verify the preview (evidence, not a gate)
Invoke verify once with Step 3's exact checkpoint receipt, plus one with the fix's receipt, never for a better verdict. No verify skill, or LOCAL → say so in one line and go on; never install it.
Any verdict but FAILURE → report it and merge. FAILURE after /verify's own fixes → one fix: apply inside /ship with ARCHIVE and the failures, then /save as in Step 3, and verify. Still FAILURE, or the fix must stop → say what fails and ask: fix more (Recommended), or publish anyway, recorded. If the walk's fixes, or its one /save of kept checks, advanced HEAD, merge that commit only when that /save returns SUCCESS or NONE.
Step 5 — merge and sync
Run finish once; allow 12 minutes. It merges, runs the project's after-merge part, and looks at the live app. A skipped sync, a secrets error, or PLAN_PAGE=skipped is a report line, not a failure. Not merged → report the error and stop, unless NEXT: gives a recovery; then finish again only on a result Step 3 proceeds on.
Merge, not rebase, unless asked. Never check out, switch, stash, reset, or force a branch to make the sync succeed, or delete a local branch.
Look at the live app
LIVE_LOOK=ok/unknown → REASON as one report line. failed → say what fails, then invoke apply once with REASON and URL as the request; it ends at its preview and publish it?. No retry or revert.
Step 6 — report
Lead with the outcome in plain words: it is live, what changed for the person, the live link, then the plan's link from build-review.mjs <name>. Always add Checks loosened, each Check: bullet in the archived Decision log, and Choices I made, each Assumed line this ship added and each MOVED= plan, one plain line each; omit when none. Only when asked, add finish's and /save's lines, the archive path, the walk's verdict and evidence (a merged-anyway FAILURE says the person chose it), and the secret key names.
Then end by next work. A failed live look, or a /ship from /close, never asks to close.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |