What problem does it solve? Teams and autonomous agents often produce chaotic git histories, inconsistent version numbers, and missing changelog entries. This Skill standardizes how versions are bumped, how CHANGELOG.md is updated, and how commits are formatted so every repository follows one uniform release protocol. ## Core Features & Use Cases - Semantic Versioning Rules: Defines exactly when to bump MAJOR, MINOR, or PATCH versions based on the type of change. - Parse-Then-Append Changelog Protocol: Reads CHANGELOG.md, locates the correct version header and category, and inserts entries without duplicating sections. - Conventional Commits Enforcement: Restricts commit messages to feat, fix, docs, refactor, or chore prefixes with a 72-character limit, validated through an MCP commit tool. - Use Case: After an agent finishes a bug fix, it bumps the PATCH version, appends a Fixed entry under the new version header in CHANGELOG.md, and closes the task with a validated fix: commit via the MCP tool instead of raw git commands. ## Quick Start Apply the versioning-and-release skill to bump the project version, update CHANGELOG.md, and create a compliant conventional commit for my latest changes.