How does this skill handle breaking changes?

The skill supports indicating breaking changes by adding a '!' after the type/scope or by including 'BREAKING CHANGE:' in the footer, which triggers a Major version bump.

What is the Conventional Commits specification?

It is a lightweight convention for commit messages that provides a set of rules for creating an explicit commit history, which makes it easier to write automated tools on top of.

Does it support types other than feat and fix?

Yes, it includes support for the Angular convention types such as build, ci, docs, perf, refactor, style, and test.

Is this skill compatible with semantic-release?

Yes, it generates messages specifically designed to be parsed by semantic-release, commitizen, and other industry-standard automation tools.

Conventional Commits Specialist

Name: Conventional Commits Specialist
Author: BbgnsurfTech

byBbgnsurfTech

•

개발자 도구

Standardizes git commit messages following the v1.0.0 specification to enable automated changelogs and semantic versioning.

소개

This skill empowers Claude to compose, validate, and review git commit messages according to the official Conventional Commits specification. By providing structured guidance on mandatory types like feat and fix, optional scopes, and breaking change indicators, it ensures your project maintains a machine-readable history. This is particularly useful for teams using automation tools like semantic-release, commitizen, or git-cliff to streamline release cycles and generate consistent, high-quality changelogs directly from the codebase history.

주요 기능

Automated composition of specification-compliant commit messages
Validation of header length, tense, and formatting rules
Support for breaking change markers via '!' syntax or footer notation
Integration guidance for commitlint and Angular-style conventions
3 GitHub stars
Mapping of commit types to Semantic Versioning (SemVer) impacts

사용 사례

Configuring CI/CD pipelines for automated versioning and changelog generation
Standardizing commit habits across a team to improve repository readability
Generating structured commit messages after completing coding tasks

소개

주요 기능

Automated composition of specification-compliant commit messages
Validation of header length, tense, and formatting rules
Support for breaking change markers via '!' syntax or footer notation
Integration guidance for commitlint and Angular-style conventions
3 GitHub stars
Mapping of commit types to Semantic Versioning (SemVer) impacts

사용 사례

Configuring CI/CD pipelines for automated versioning and changelog generation
Standardizing commit habits across a team to improve repository readability
Generating structured commit messages after completing coding tasks