conventional-commits

Write conventional commit messages with type prefixes, scope, and body blocks.

Updated Feb 11, 2026

Search Tags:#git #coding-standards #lint #semantic-versioning #commit-message #conventional-commits

Ready to run

npx skills add https://github.com/kabaka/cpap-analyzer --skill conventional-commits-kabaka

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: conventional-commits
Source: https://github.com/kabaka/cpap-analyzer/tree/main/.github/skills/conventional-commits
Command: npx skills add https://github.com/kabaka/cpap-analyzer --skill conventional-commits-kabaka

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill standardizes commit messages across a codebase by enforcing the Conventional Commits specification, improving changelogs, versioning, and collaboration.

Core Features & Use Cases

Type prefixes (feat, fix, docs, chore, refactor, test, perf, ci, style, build) ensure consistent commit semantics.
Optional scope to indicate the affected module or feature.
Subject and body guidance to keep messages concise and informative, enabling automated tooling.

Quick Start

Use the conventional commits format to craft a new feature commit message.

Frequently Asked Questions about conventional-commits

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

FAQPage Schema

How do I write a conventional commit message for a new feature?▼

Conventional commits standardize project history by applying type prefixes like 'feat' or 'fix', an optional scope, and structured subject and body blocks. This ensures consistent commit semantics across Git-based workflows to improve versioning and collaboration.

What is the conventional commits specification and how does it work?▼

The conventional commits specification standardizes commit messages by enforcing type prefixes, optional scope, and structured body or footer blocks. This semantic formatting enables automated tooling to parse commit history for changelog generation and semantic versioning.

How do I structure commit messages to automate semantic versioning?▼

To automate semantic versioning, structure commit messages using type prefixes like 'feat' for features or 'fix' for bug fixes, along with an optional scope and subject. This semantic format allows automated tooling to determine version bumps and generate changelogs.

Does the conventional commits format work with existing Git workflows?▼

The conventional commits format applies directly to Git-based workflows across standard commits and pull requests. It standardizes project history by implementing type prefixes and structured blocks without altering your underlying version control process.

What commit type prefixes should I use for docs or refactoring?▼

For docs or refactoring, use the 'docs' or 'refactor' type prefixes in your conventional commit messages. The full specification also supports 'feat', 'fix', 'chore', 'test', 'perf', 'ci', 'style', and 'build' to ensure consistent commit semantics across your codebase.