What commit types are included by default?

It includes the core 'feat' and 'fix' types, alongside common types like 'chore', 'docs', 'style', 'refactor', 'perf', 'test', 'build', 'ci', and 'revert'.

Can I use specific scopes for my commits?

Yes, the skill allows for optional scoping (e.g., 'feat(auth):') to specify exactly which part of the codebase is affected by the change.

Is it compatible with tools like semantic-release?

Absolutely. It generates the exact machine-readable format required by semantic-release, commitizen, and git-cliff for automated versioning.

Does this skill support breaking changes?

Yes, it fully supports both the '!' prefix in the header and the 'BREAKING CHANGE:' footer notation required by the v1.0.0 specification.

How does it help with Semantic Versioning (SemVer)?

The skill maps 'fix' to PATCH, 'feat' to MINOR, and any BREAKING CHANGE to MAJOR version bumps, ensuring your versioning reflects the actual impact of changes.

Conventional Commits

Name: Conventional Commits
Author: Jamie-BitFlight

byJamie-BitFlight

•

Developer Tools

Standardizes Git commit messages to enable automated semantic versioning and professional changelog generation.

About

This skill empowers Claude to compose, validate, and manage Git commit messages following the Conventional Commits v1.0.0 specification. By enforcing structured prefixes like feat and fix, and identifying breaking changes, it ensures a machine-readable project history. This facilitates seamless integration with automation tools like semantic-release and git-cliff, allowing teams to automate versioning and documentation while maintaining a clear, readable record of codebase evolution.

Key Features

Semantic Versioning (SemVer) correlation for automated release management
Validation of commit headers against the 72-character imperative-tense standard
Automated commit message drafting following Conventional Commits v1.0.0
Standardized identification of BREAKING CHANGEs via footer or '!' syntax
11 GitHub stars
Support for Angular-style types including refactor, perf, chore, and ci

Use Cases

Refactoring messy commit histories into structured, specification-compliant logs
Enforcing consistent commit standards across distributed engineering teams
Preparing repositories for automated changelog generation and CI/CD releases

About

Key Features

Semantic Versioning (SemVer) correlation for automated release management
Validation of commit headers against the 72-character imperative-tense standard
Automated commit message drafting following Conventional Commits v1.0.0
Standardized identification of BREAKING CHANGEs via footer or '!' syntax
11 GitHub stars
Support for Angular-style types including refactor, perf, chore, and ci

Use Cases

Refactoring messy commit histories into structured, specification-compliant logs
Enforcing consistent commit standards across distributed engineering teams
Preparing repositories for automated changelog generation and CI/CD releases