What are Conventional Commits?

Conventional Commits is a lightweight convention for commit messages that provides a set of rules for creating an explicit commit history, making it easier for people and tools to understand.

Does this skill help with automated changelogs?

Yes, by standardizing types like 'feat' and 'fix', it ensures your commit history can be easily parsed by tools like semantic-release to generate automated changelogs.

Why does this skill emphasize the imperative mood?

The imperative mood (e.g., 'add' instead of 'added') follows Git's built-in conventions and describes what the commit will do to the codebase when applied.

What is the ideal length for a commit subject?

The ideal length is 50 characters or less for the subject line, with a maximum of 72 characters to ensure the message isn't truncated in Git logs.

Conventional Commit Styler

Name: Conventional Commit Styler
Author: phrazzld

byphrazzld

•

Developer Tools

Standardizes Git commit messages using the Conventional Commits format to ensure a clean, readable, and machine-parsable repository history.

About

This skill equips Claude with the expertise to draft, review, and refine Git commit messages following the industry-standard Conventional Commits specification. By enforcing the imperative mood, specific type prefixes (such as feat, fix, and refactor), and character limits, it helps teams maintain a professional project history that is easy to search and ready for automated changelog generation. It is particularly useful when preparing pull requests, documenting complex architectural changes, or ensuring consistency across a multi-developer codebase.

Key Features

Automated Conventional Commits formatting (feat, fix, refactor, etc.)
Enforcement of the imperative mood and 50-character subject limits
Support for breaking change annotations and issue tracking references
Guidance on writing descriptive bodies that explain the 'why' behind changes
Validation of scope and footer metadata for structured history
2 GitHub stars

Use Cases

Drafting clear and professional commit messages during active development
Generating structured metadata to support automated release notes
Reviewing Git history to standardize non-compliant messages

About

Key Features

Automated Conventional Commits formatting (feat, fix, refactor, etc.)
Enforcement of the imperative mood and 50-character subject limits
Support for breaking change annotations and issue tracking references
Guidance on writing descriptive bodies that explain the 'why' behind changes
Validation of scope and footer metadata for structured history
2 GitHub stars

Use Cases

Drafting clear and professional commit messages during active development
Generating structured metadata to support automated release notes
Reviewing Git history to standardize non-compliant messages