Semver review
Review a diff, changelog, pull request, or release plan for Semantic Versioning 2.0.0 compliance and recommend the minimum safe version bump. Use for release reviews, breaking-change checks, changelog audits, and version-bump verification.From its SKILL.md
npx -y skills add LenoSeibert/semver-plugin --skill semver-reviewAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.5 KB, as published. Nobody here has run it
SemVer Release Review
Inspect the public API definition and the actual changes. Include documented interfaces such as libraries, CLIs, protocols, file formats, configuration, schemas, and observable behavior when consumers can depend on them.
Review
- Identify the current released version and public API boundary.
- List consumer-visible changes, separating incompatible changes, backward-compatible features/deprecations, fixes, and internal-only work.
- Select the highest required bump using SemVer 2.0.0.
- Verify that lower components reset, the proposed version has not already been released, and pre-release/build labels are valid when used.
- Flag uncertainty when compatibility cannot be established from evidence.
Do not downgrade a bump because a break seems small, optional, or easy to
migrate. Do not upgrade a bump merely because the implementation diff is
large. Under 0.y.z, report that SemVer permits arbitrary change and evaluate
the repository's documented pre-1.0 policy separately.
Output
Lead with Recommendation: <version or bump>. Then give only evidence-backed
findings, highest severity first, with file locations when reviewing a repo.
End with missing evidence or No SemVer blockers found.