versioning-and-release

Enforces SemVer versioning, Keep a Changelog entries, and Conventional Commits across repositories.

6|Updated May 18, 2026
One-click install
npx skills add https://github.com/mokhtarabadi/cognitive-lead-hq --skill versioning-and-release-mokhtarabadi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: versioning-and-release
Source: https://github.com/mokhtarabadi/cognitive-lead-hq/tree/main/skill-templates/versioning-and-release
Command: npx skills add https://github.com/mokhtarabadi/cognitive-lead-hq --skill versioning-and-release-mokhtarabadi

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about versioning-and-release

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I decide between a MAJOR, MINOR, or PATCH version bump?▼

Use PATCH for bug fixes and documentation syncs, MINOR for new features, skills, or non-breaking upgrades, and MAJOR for breaking API changes or complete rewrites. The Skill defines these SemVer rules explicitly for every repository.

How do I add an entry to CHANGELOG.md without duplicating sections?▼

Follow the Parse-Then-Append protocol: read the file, find the target version header, then the category, and append the bullet. Create missing categories in canonical order and never duplicate a category under one version.

What commit message format does Conventional Commits require?▼

Messages must start with a lowercase prefix from feat, fix, docs, refactor, or chore, followed by a colon and a description of at most 72 characters. The MCP commit tool validates this format and rejects free-form text.

Can agents run git commit or git push directly?▼

No. The Zero-Autonomous-Commit policy forbids raw git commit and push. Agents must call the custom_context_commit_and_clean_task MCP tool, and only the Manager pushes to the remote manually after task closure.

What happens to the Unreleased section after a release?▼

The [Unreleased] section must be empty after a release. All entries are moved under the new version header, and metadata-only releases must explicitly state that system-prompt.md version is unchanged.