ship

Invoke the ship skill on your branch and it runs tests, reviews the diff, bumps the version, generates a changelog, creates an annotated git tag, and pushes. Use flags like patch, minor, or major to control the bump type explicitly.

It detects the current branch: on main, master, trunk, or develop it uses direct flow with tag and push, while any other branch triggers PR flow targeting the repository's default branch. Repo-level conventions in project docs override the branch-name heuristic.

No, there is no review-skip flag. Small diffs under 20 lines automatically take a fast review path via the threshold table, but review itself is mandatory and unskippable for all release sizes.

Failures are triaged into new regressions, pre-existing failures, or environment issues. New regressions are fixed in-run, trivially fixable pre-existing failures are fixed in a separate commit, and environment failures trigger a capped re-run before the pipeline continues.

Yes, the --dry-run flag walks through every phase printing what would happen — branch, flow, diff size, review depth, bump type, staged files, tag name, and push target — without executing anything.

The skill detects half-completed releases by scanning recent history for untagged release commits. It skips re-bumping, reconstructs the missing tag at the original commit, and resumes the pipeline at the tag and push steps.