Command
/shipmates-release
changelog → CI-green tag → (opt-in) publish
Changelog, version bump, green CI, then tag — publish if you say so.
See it run
/shipmates-release runs, in order.How to run it
Run it in your harness
/shipmates-release [version — e.g. v1.4.0, or "patch"/"minor"/"major" to derive it]<angle brackets> = required · [square brackets] = optional
How it works
The writer assembles notes from what actually merged. SRE checks rollback and migration safety before anything is tagged. Publish is opt-in.
Since last tag
Collect every merged PR and commit since the last release.
No specialist — the run reads git history.
Notes + bump
Write the changelog from that history and move the version files together.
Crew
Gate
CI must be green on the exact commit you will tag. SRE checks rollback and migration safety.
Ship
Tag it. Publish a GitHub release only when you opt in.
No extra spawn — tag and optional publish.
When to use
- Merged work is ready as a named version with notes.
- A single feature PR that should bump version? That lives in /ship-issue.
The skill
The installer ships the full skill — stages, gates, config — from commands/shipmates-release.md.