conventional-commits

Format commit messages to conform to the Conventional Commits specification.

6|Updated Jan 12, 2026
One-click install
npx skills add https://github.com/bastos/skills --skill conventional-commits-bastos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: conventional-commits
Source: https://github.com/bastos/skills/tree/main/conventional-commits
Command: npx skills add https://github.com/bastos/skills --skill conventional-commits-bastos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Format commit messages to follow a standardized convention, enabling automated changelog generation, semantic versioning, and clearer project history.

Core Features & Use Cases

  • Enforces type prefixes (feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert) in commit messages
  • Supports optional scopes to provide contextual information about changes
  • Integrates with tooling to generate changelogs, determine version bumps, and validate commit history

Quick Start

Start composing commits using the conventional format, for example: feat(auth): add OAuth support

Frequently Asked Questions about conventional-commits

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

FAQPage Schema
How do I format git commit messages for automated changelog generation?

Conventional Commits formatting structures git commit messages with required type prefixes, optional scopes, and body footers to ensure consistent, machine-readable project history for automated changelog generation.

What are the required type prefixes for conventional commit messages?

The required type prefixes for conventional commit messages include feat, fix, docs, style, refactor, perf, test, build, ci, chore, and revert, which categorize changes to enable automated semantic versioning and clearer project history.

How do I write a conventional commit with a scope?

To write a conventional commit with a scope, you append the scope in parentheses directly after the type prefix, such as 'feat(auth): add OAuth support', providing contextual information about the specific module affected by the change.

Does conventional commit formatting work with semantic versioning?

Yes, conventional commit formatting works with semantic versioning by integrating with tooling that parses commit types like feat and fix to automatically determine version bumps and validate the commit history.

Can I use conventional commits for code reviews?

Yes, you can use conventional commits for code reviews because the standardized type prefixes and optional scopes provide immediate contextual information about the nature and impact of changes, making the review process more efficient.