Menu
Run pre-release checks, pick the version bump, and cut the release. Use when ready to tag and release.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Create and update AGENTS.md project rules. Use when authoring or amending the cross-tool conventions agents must follow.
Write forward-looking startup instructions for the next session, then reset context to save costs. Use when the context is getting long or before switching focus.
Create and maintain a specification that states what to build, not how. Use when writing a spec, editing requirements, or defining acceptance criteria.
Run all review dimensions against a diff or a path. Use when reviewing a feature branch before merge, reviewing someone else's PR, or auditing a file path.
Create or update project documentation. Use when creating architecture docs, runtime docs, reference docs, or design documents that explain what the system does.
Review architecture, boundaries, and design consistency. Use when reviewing module boundaries, extension seams, or contract drift.
| name | ship |
| description | Run pre-release checks, pick the version bump, and cut the release. Use when ready to tag and release. |
Run a structured pre-release gate, determine the version bump from the commits, and cut the release. This is a release gate over the whole project, not a diff review — review already happened.
The skill orchestrates and gates; the release mechanics belong to the project. Read AGENTS.md for the verify and release commands, and defer to them — the release entry point (a script or CI workflow) owns the version bump, changelog, tag, and any project-specific pre-release gates. Where none exists, take the manual path in the workflow. The release shape varies by ecosystem — tag-and-bump, or build-and-publish a checksummed artifact — and this skill assumes none. Where the project has no release entry point, take the manual path in the workflow.
Check the entire project against the preconditions below. Never push; the last human step is pushing the tag.
main unless the project says otherwise)AGENTS.md).env files for common key shapes (sk-, Bearer , -----BEGIN, provider API-key env names)handoff and re-running in a fresh session, so the gate starts from a compact summary rather than a saturated context.TODO / FIXME left in non-test sourcefeat subjects; defer drift detail to doc-reviewgit describe --tags --abbrev=0 --match 'v[0-9]*'git log <prev_tag>..HEAD --oneline --no-mergesBREAKING CHANGE in the body or ! before the colon in the subjectfeat(...) or feat:v<version>.<level> — reason)agents-md — where the project's verify and release commands are declaredreview — the quality gate that runs before ship; ship assumes it passedgit — commit conventions the version bump reads fromdoc-review — user-facing drift before the taghandoff — compact the context before a release that follows a long session