What problem does it solve?
Incorrectly applying semantic versioning (SemVer) can lead to broken builds, unexpected compatibility issues, and confusion among developers. This Skill eliminates the guesswork from versioning, providing clear, accurate advice on how to classify changes and determine the correct MAJOR, MINOR, or PATCH bump for your releases and dependencies.
Core Features & Use Cases
- Version Change Classification: Automatically determines if a version update is MAJOR, MINOR, or PATCH based on SemVer rules, with clear explanations.
- Version Bump Recommendation: Advises on the appropriate version increment (MAJOR, MINOR, PATCH) based on a list of changes, ensuring consistency.
- Version Proposal Validation: Checks if a proposed version bump is valid according to SemVer rules, including segment resets and change severity matching.
- Use Case: Before releasing a new library version, provide a list of changes (e.g., "fixed bug X, added feature Y, removed API Z"). The Skill will tell you if it should be a MAJOR, MINOR, or PATCH release and why.
Quick Start
Classify the version change from 1.2.3 to 2.0.0. Explain why.