git-conventional-commit

To generate conventional commit messages for staged Git changes, prompt the AI to analyze your staged diffs and draft a type(scope)!: summary structure. A helper script at ./scripts/compose-conventional-commit.sh can also generate a commit skeleton automatically.

The conventional commit format for Git version control enforces a standard structure of type(scope)!: short summary to improve readability and tooling compatibility. It requires choosing the narrowest type and scope while keeping subject lines concise.

To add a BREAKING CHANGE footer to a conventional commit, guide the AI to append the breaking-change guidance to your drafted message when major modifications are detected in the staged diff. This ensures pre-commit checks pass successfully.

Yes, you can use a shell script to draft conventional commit skeletons automatically. The Skill provides a helper script at ./scripts/compose-conventional-commit.sh specifically designed to generate the initial commit message structure for your workflow.

No, this conventional commit workflow does not require any external Git dependencies. It operates independently to analyze staged changes and draft messages that satisfy type, scope, and breaking-change guidance without additional package installations.

Your conventional commit pre-commit checks keep failing because the message structure likely violates the required type(scope)!: summary format. Using the AI to draft the message or the helper script ensures the narrowest type and concise subject line are applied correctly.