What problem does it solve? Teams often release software with inconsistent version numbers, mismatched version strings across files, and unclear branch conventions. This Skill standardizes how AI agents manage git branches, semantic versions, and release declarations so every release follows the same rules. ## Core Features & Use Cases - Semantic Versioning Rules: Defines when to increment MAJOR, MINOR, or PATCH versions with concrete examples for features, fixes, and releases. - Version Consistency Enforcement: Requires package.json, index.html, README.md, and git tags to always match, with git tags as the single source of truth. - Branch and Release Governance: Mandates feature/<name> and fix/<name> branch patterns, forbids direct work on main, and requires a release type declaration plus a pre-release checklist. - Use Case: Before merging a new audio system, the agent creates feature/audio-system, declares Release Type: MINOR, bumps v0.3.5 to v0.4.0 across all version files, creates the git tag, and completes the release checklist. ## Quick Start Ask the agent to create a new release branch and bump the project version following the versioning rules before opening a merge request.
