What problem does it solve? Teams ship inconsistent versions: breaking changes hidden in minor bumps, hand-edited version numbers drifting across files, tags pushed from laptops, and changelogs that are raw git logs. This Skill establishes a disciplined release process where version numbers are honest promises to consumers and the mechanics are automated. ## Core Features & Use Cases - Semver Decision Framework: Bump major/minor/patch by consumer impact, not effort, with a written definition of the public API surface in VERSIONING.md. - Release Automation: Wire Conventional Commits with release-please, semantic-release, or changesets so version, tag, and changelog generate from commit metadata. - Tag & Changelog Protocol: CI-created annotated immutable tags triggering publish workflows, plus keep-a-changelog format that is generated then human-edited. - Use Case: A CLI tool stuck at 0.9.x breaking users each minor defines its contract, cuts 1.0.0, wires changesets, and ships a renamed flag as 2.0.0 with a deprecated alias — zero surprise breakage. ## Quick Start Set up automated semver releases with conventional commits and CI-created tags for my project.