Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Use when cutting a stable/production release of THIS project. Fires on: "cut a release", "bump the version", "tag a release", "ship to prod", "release notes". Determines the semver bump from merged PRs, updates version files, generates a changelog, and tags. Distinct from bump-deps (incoming deps vs outgoing version).
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-05 | ✗→✓ | ▲ Improved | 57% | 0% |
| case-07 | ✗→✓ | ▲ Improved | -48% | 0% |
| case-13 | ✗→✓ | ▲ Improved | -53% | 0% |
| case-03 | ✓→✓ | = Same ✓ | -24% | 0% |
| case-04 | ✓→✓ | = Same ✓ | -48% | 0% |
This is about the project's OWN version, not its dependencies. Reproducible and deliberate — production cadence, not a routine merge.
fix only → patch. State the reasoning from the delta; ask the user if the delta is ambiguous rather than guessing major/minor.
about screen, __version__, etc.). Consult .skills/change-map.yaml for a "project version" coupling if present.
grouped (Added / Changed / Fixed). Link PRs.
a red build.
deploy is outward-facing — confirm with the user before pushing.
The chosen version + why, the changelog section, files bumped, and the tag command (executed only after the user confirms the push). Stop before any irreversible publish step and ask.
Other measured skills in the registry, with their headline benchmark lift.