Which commit types are supported by this skill?

The skill supports all standard types including feat, fix, docs, style, refactor, perf, test, and chore, as well as build, ci, and revert.

Does it follow the 50/72 character rule for Git?

Yes, the skill encourages keeping the description under 50 characters and wrapping the body at 72 characters to ensure compatibility with Git log tools.

How does this skill handle breaking changes?

It implements the Conventional Commits standard for breaking changes by using the '!' suffix after the type/scope or by adding a 'BREAKING CHANGE:' footer.

Can I reference GitHub issues or Jira tickets?

Yes, the skill provides specific formatting for footers such as 'Fixes #123' or 'Closes #456' to link commits directly to issues.

Conventional Commits Workflow

Name: Conventional Commits Workflow
Author: dgalarza

bydgalarza

•

Developer Tools

Standardizes Git commit messages using the Conventional Commits specification for improved project history and automation.

About

This skill empowers Claude to author and review Git commit messages following the Conventional Commits v1.0.0 specification, ensuring your project history remains clean and machine-readable. By providing structural guidance for commit types, scopes, and breaking changes, it facilitates the use of automated tools for changelog generation and semantic versioning. Whether you are committing a small bug fix or a major feature, this skill helps maintain a professional, consistent audit trail that improves team collaboration and long-term project maintainability.

Key Features

Automatic formatting of commit types, scopes, and descriptions
Support for breaking change flags and detailed footers
Validation of imperative mood and character length constraints
Co-author credit formatting for collaborative development
13 GitHub stars
Integration of issue and pull request references

Use Cases

Reviewing existing repository history for compliance with the specification
Generating clear and structured commit messages for new code changes
Preparing release notes by categorizing changes into machine-readable types

About

Key Features

Automatic formatting of commit types, scopes, and descriptions
Support for breaking change flags and detailed footers
Validation of imperative mood and character length constraints
Co-author credit formatting for collaborative development
13 GitHub stars
Integration of issue and pull request references

Use Cases

Reviewing existing repository history for compliance with the specification
Generating clear and structured commit messages for new code changes
Preparing release notes by categorizing changes into machine-readable types