formatting-commit-messages

To format git commit messages for Conventional Commits, the skill analyzes staged diffs to detect change types, scope, and breaking changes, then outputs a properly formatted message. It automatically determines the appropriate type prefix like feat, fix, or docs.

Generating consistent commit messages for automated release notes requires following the Conventional Commits specification. This skill analyzes your staged changes to produce structured messages, signaling breaking changes with a '!' suffix to enable reliable release note generation.

To detect breaking changes in staged git diffs, the skill analyzes the changes and checks for modifications that require a '!' suffix per the Conventional Commits spec. It then generates a properly formatted commit message signaling the breaking change for user approval.

Yes, you can automatically determine the correct type prefix for conventional commits. The skill analyzes staged diffs to identify the nature of the changes and assigns the appropriate type prefix such as feat, fix, or docs, along with an optional scope.

Yes, this commit formatting approach works with standard git workflows. It is used during commit workflows to analyze staged changes and generate consistent conventional commit messages for features, fixes, docs, or release notes in your codebases.

Conventional commit messages lack correct scope and breaking change indicators when not properly analyzed. This skill evaluates staged diffs to detect the appropriate scope and appends the '!' suffix for breaking changes, ensuring the output message meets the specification.