conventional-commits

To enforce conventional commits in Git, this Skill validates commit messages against the specification by checking for the required type, optional scope, and description format. It integrates as a pre-commit hook to reject non-compliant messages before code is committed.

The correct format for conventional commit messages is `type(scope): description`. This Skill validates that your messages use strict formatting with specific rules for types like 'feat' for features, 'fix' for bug fixes, and 'BREAKING CHANGE' for major updates.

Semantic versioning with conventional commits works by using commit message types to determine version bumps automatically. This Skill ensures your commits follow the specification, enabling predictable release processes and automated changelog generation based on 'feat' or 'fix' types.

Yes, you can use this Skill to enable automated changelog generation from Git commit history. By validating that every commit message strictly follows the conventional commits specification, it ensures your Git log contains the structured data needed for reliable changelog automation.

This commit message validator supports optional scopes and specific rules for breaking changes. It enforces the conventional commits specification by checking the `type(scope): description` structure and verifying that 'BREAKING CHANGE' footers are formatted correctly.

Your Git commits are being rejected because the pre-commit hook detected messages that do not follow the conventional commits specification. This Skill enforces the strict `type(scope): description` format, rejecting commits lacking valid types like 'feat', 'fix', or 'chore'.