semver
Installation
SKILL.md
semver
Answer the question people get wrong: is this change breaking, and therefore what is the next version? The spec is trivial; the judgment is not. This skill decides the bump from evidence, then applies it. It is repo-agnostic: it works on any project that has versioning.
The rule (and the 0.x asterisk)
Given the last released version and the change since it:
| Bump | Meaning | Trigger |
|---|---|---|
| MAJOR | Breaking | anything a working consumer depends on could stop working (checklist below) |
| MINOR | Feature | backward-compatible addition (new API / flag / optional field) |
| PATCH | Fix | behavior-preserving change (bugfix, docs, perf, internal refactor) |
Pre-1.0 (0.y.z): no compatibility guarantees. By convention, bump MINOR for a breaking change and PATCH for everything else until you commit to 1.0. State which convention the project follows before recommending.