semver

What problem does it solve?

Ensures consistent, correct semantic version increments by classifying changes as major, minor, or patch so releases communicate compatibility expectations and avoid breaking downstream consumers.

Core Features & Use Cases

• Major (breaking changes): Rules to identify incompatible API, CLI, configuration, or runtime removals and signature changes that require a major version bump.
• Minor (backward-compatible additions): Guidance for adding new endpoints, optional parameters, commands, or opt-in features that extend functionality without breaking existing consumers.
• Patch (backward-compatible fixes): Criteria for bug fixes, security patches, performance improvements, and internal refactors that do not change the public interface.
• Use Cases: Classify pull requests during code review, automate CI release tags, determine version bumps for changelogs, and advise on dependency or platform support removals.

Quick Start

Ask the semver skill to assess a pull request description and recommend major, minor, or patch based on the described changes.