releaselisted
Install: claude install-skill Udhay-Adithya/skills
# Release
Derive the version, report it, then wait. Never bump a version unprompted.
## 1. Find the last release
```bash
git fetch --tags
git describe --tags --abbrev=0
git log "$(git describe --tags --abbrev=0)"..HEAD --oneline --no-merges
```
With no tags yet, the range is the whole history and the first release is `0.1.0`
unless told otherwise.
## 2. Derive the bump
Read the Conventional Commit type of every commit in that range:
| Found in the range | Bump |
| --- | --- |
| Any `!` before the colon, or a `BREAKING CHANGE:` footer | major |
| Otherwise, any `feat` | minor |
| Otherwise (`fix`, `perf`, `refactor`, `docs`, `test`, `build`, `ci`, `chore`, `style`, `revert`) | patch |
Below `1.0.0` the API is unstable, so a breaking change may land in a minor bump
instead of taking the project to `1.0.0`. Going to `1.0.0` is a deliberate decision
about stability, never a side effect of a commit type. From `1.0.0` on, a breaking
change needs a major bump.
Pre-release and build metadata follow the spec: `1.4.0-beta.1`, `1.4.0+20260115`.
A commit whose message does not parse as a Conventional Commit is a problem worth
naming. Do not silently treat it as a patch: list it and say the bump was derived
without it.
## 3. Report and stop
Say the derived version, the bump level, and the commits that drove it, with the
breaking ones called out. Then wait for a decision. The derivation is the deliverable;
the bump is a separate instruction.
## 4. Land the bump
Once approved,