release-bumplisted
Install: claude install-skill tony/ai-workflow-plugins
# Bump to the Next Version
Discover the project's current version and versioning scheme, work out
what "next" means, get the user's explicit choice, then run the full
the `release-cut` skill procedure at the chosen version.
Arguments: $ARGUMENTS
First, read `references/release-conventions.md`.
The safety contract in the `release-cut` skill applies
here unchanged: no push, no tag, no tag push without the explicit
flags.
---
## Phase 1: Discover the Current Position
Gather three signals and check they agree:
1. **Manifest version** — from the version-bearing files (conventions
reference).
2. **Latest tag** — `git tag --sort=-creatordate | head -20`, noting
the prefix convention and the increment vocabulary the project has
actually used (aN, bN, rcN, postN, devN, `-next.N`, plain semver).
3. **CHANGES unreleased header** — the version it already targets.
A stable-track header like `## <project> 0.63.x (unreleased)`
constrains the next release to the `0.63` series unless the user
overrides; a prerelease-track header names the next version
outright.
If the signals disagree (manifest ahead of tags, CHANGES targeting a
different series), surface the discrepancy before proposing anything.
## Phase 2: Enumerate Candidates
Build the candidate list from the project's scheme — concrete
versions, not abstract bump names:
- **Prerelease track** (e.g. current `0.1.9a1`):
- Next prerelease: `0.1.9a2` — the routine increment
- Graduate to final: `0.1.9`
-