Does it support multi-line commit messages?

Yes, it uses a shell-safe heredoc format to allow for detailed bodies and footers while preventing issues with shell expansion during the commit process.

Does this skill add AI-generated signatures to my commits?

No. This skill strictly adheres to professional standards and never adds tool attributions, signatures, or 'Generated with Claude' messages to your Git history.

Can I link my commits to specific issues?

Yes, the skill supports various issue reference keywords like 'Fixes #123', 'Closes #456', or 'Relates to #789' to provide traceability between your code and tasks.

How does this skill handle breaking changes?

The skill adds a '!' after the type/scope and includes a 'BREAKING CHANGE:' footer with migration instructions to ensure the breaking change is properly documented and machine-readable.

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 to write automated tools on top of.

Advanced Conventional Commits

Name: Advanced Conventional Commits
Author: acbcdev

byacbcdev

Developer Tools

Generates standardized, professional Git commit messages following the Conventional Commits specification for complex development scenarios.

About

This skill empowers developers to maintain a pristine project history by automating the creation of Conventional Commits directly within the Claude Code environment. It intelligently analyzes staged changes to determine the appropriate type and scope, handles breaking changes with the correct syntax, and manages issue references for better project tracking. By enforcing industry best practices—such as imperative mood, character limits, and structured footers—it ensures your repository's log remains readable, machine-parseable, and professional, making it an essential tool for teams using automated versioning or changelog generation.

Key Features

Intelligent analysis of staged changes to suggest correct commit types and scopes
Support for breaking changes with '!' markers and structured BREAKING CHANGE footers
Automatic linking to issue trackers using Fixes, Closes, and Relates syntax
Multi-line commit message generation using shell-safe heredoc formatting
Strict enforcement of git log best practices including imperative mood and length limits
0 GitHub stars

Use Cases

Documenting complex feature releases that involve breaking API changes
Ensuring parseable commit history for automated semantic versioning and changelog tools
Standardizing commit messages across a multi-developer team to maintain repository health

About

Key Features

Intelligent analysis of staged changes to suggest correct commit types and scopes
Support for breaking changes with '!' markers and structured BREAKING CHANGE footers
Automatic linking to issue trackers using Fixes, Closes, and Relates syntax
Multi-line commit message generation using shell-safe heredoc formatting
Strict enforcement of git log best practices including imperative mood and length limits
0 GitHub stars

Use Cases

Documenting complex feature releases that involve breaking API changes
Ensuring parseable commit history for automated semantic versioning and changelog tools
Standardizing commit messages across a multi-developer team to maintain repository health