How does this skill handle breaking changes?

The skill can indicate breaking changes in two ways: by adding a '!' after the type/scope (e.g., feat!) or by including a 'BREAKING CHANGE:' footer in the commit body.

Does it support the Angular commit message format?

Yes, it includes all recommended types from the Angular convention, such as build, ci, docs, perf, refactor, style, and test.

Will this help with automated releases?

Absolutely. By using this skill to format commits, your repository becomes compatible with tools like semantic-release and git-cliff which automate the entire release process based on commit history.

What is the primary benefit of using Conventional Commits?

It provides a lightweight convention on top of commit messages, creating a machine-readable history that allows for automated versioning, changelog generation, and better communication of changes to stakeholders.

Conventional Commits

Name: Conventional Commits
Author: Jamie-BitFlight

byJamie-BitFlight

•

개발자 도구

Standardizes git commit messages following the Conventional Commits v1.0.0 specification to enable automated versioning and changelog generation.

소개

The Conventional Commits skill empowers Claude to compose structured, specification-compliant git commit messages that are both human-readable and machine-parsable. By enforcing standardized types, optional scopes, and breaking change indicators, this skill facilitates seamless integration with automation tools like semantic-release, commitizen, and git-cliff. It ensures your project history remains clean and professional while automatically correlating code changes to Semantic Versioning (SemVer) increments, making it an essential utility for modern CI/CD workflows and collaborative software development.

주요 기능

Enforces imperative mood and present tense for professional commit summaries
Identifies and formats breaking changes using '!' or footer notation
Maps commit types directly to Semantic Versioning (Major, Minor, Patch) impacts
Supports standard Angular types including feat, fix, chore, refactor, and more
10 GitHub stars
Composes specification-compliant commit headers with type, scope, and description

사용 사례

Automating the generation of project changelogs from git history
Configuring CI/CD pipelines for automated semantic version bumping
Enforcing consistent commit message standards across distributed teams

소개

주요 기능

Enforces imperative mood and present tense for professional commit summaries
Identifies and formats breaking changes using '!' or footer notation
Maps commit types directly to Semantic Versioning (Major, Minor, Patch) impacts
Supports standard Angular types including feat, fix, chore, refactor, and more
10 GitHub stars
Composes specification-compliant commit headers with type, scope, and description

사용 사례

Automating the generation of project changelogs from git history
Configuring CI/CD pipelines for automated semantic version bumping
Enforcing consistent commit message standards across distributed teams