git-commit-helper

To generate conventional commit messages for staged changes, provide a description of the modification and the agent will draft a standardized message. This handles types like feat, fix, and docs, along with optional scopes and breaking-change footers.

The conventional commits format standardizes project history using a specific syntax for types, scopes, and footers. You need breaking change footers when introducing backward-incompatible modifications, ensuring the message is machine-readable for automated changelogs.

Yes, you can rewrite existing commit messages to meet conventional commits rules. The agent refines your current text by adding appropriate body text, types, scopes, and breaking-change footers as needed for automation and changelog tooling.

Yes, this approach supports optional scopes and automated changelog generation. It strictly adheres to conventional commits syntax, producing machine-readable messages that integrate seamlessly with automated changelog tools used by enforcing teams.

The best way to standardize git commit history across a team is to enforce the conventional commits spec for all staged changes. This ensures consistent formatting with proper types and breaking-change footers, enabling automated changelog generation.