Conventional Commits

Standardize git commit messages for automated semantic versioning and changelog generation.

1|Updated Dec 23, 2025

Search Tags:#automation #git #changelog #versioning #commits #semver

Ready to run

npx skills add https://github.com/jonnymuir/Umbraco.Prism --skill conventional-commits-jonnymuir

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Conventional Commits
Source: https://github.com/jonnymuir/Umbraco.Prism/tree/main/.claude/skills/conventional-commits
Command: npx skills add https://github.com/jonnymuir/Umbraco.Prism --skill conventional-commits-jonnymuir

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the issue of inconsistent commit history, which prevents automated tools from accurately determining version bumps and generating reliable release notes.

Core Features & Use Cases

Semantic Versioning Automation: Maps commit types to patch, minor, or major version increments.
Breaking Change Detection: Provides a standardized syntax to flag breaking changes for downstream consumers.
Use Case: When a developer refactors a core API, they use this convention to ensure the release pipeline automatically triggers a major version bump and highlights the change in the changelog.

Quick Start

Ask the AI to format your current changes into a conventional commit message that correctly reflects the scope and impact of your work.

Frequently Asked Questions about Conventional Commits

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

FAQPage Schema

How do I standardize git commit messages for automated semantic versioning?▼

To standardize git commit messages for automated semantic versioning, you apply specific commit types and breaking change flags so release engines can accurately calculate version bumps and generate changelogs.

Why does inconsistent commit history prevent automated changelog generation?▼

Inconsistent commit history prevents automated changelog generation because release tools lack standardized syntax to parse changes, making it impossible to accurately determine whether to trigger patch, minor, or major version increments.

How do I format a git commit message to trigger a major version bump?▼

To trigger a major version bump with a git commit message, you use a standardized convention to flag breaking changes, ensuring the release pipeline detects the impact and highlights it in the changelog.

What is the best way to map git commit types to patch, minor, or major version increments?▼

Mapping git commit types to patch, minor, or major version increments requires standardizing your commit message formatting, allowing downstream automation to parse the scope and impact of your work accurately.

Do I need specific commit types for release management automation?▼

Yes, release management automation requires adherence to specific commit types and breaking change flagging to ensure accurate version calculation and reliable release notes generation by the release engine.