commit-message-formatter

Conventional commits format messages with a type (feat, fix, chore, docs, style, refactor, perf, test), optional scope, imperative subject under 50 characters, body wrapped at 72 characters, and optional footer for issues and breaking changes. This standardizes your git history for readability and changelog generation.

Inconsistent commit messages obscure code changes, break changelog generation, complicate bug tracing, and fragment team collaboration. Standardized conventional commits create a searchable, maintainable history that clarifies intent and impact of each change.

Yes. Automated commit formatting includes Claude Code co-authorship footers and links to related issues or stories when configured. This ensures consistent attribution and traceability across your project without manual entry.

Conventional commits use structured types and footers that tools parse automatically to generate changelogs, version bumps, and release notes. This eliminates manual documentation work and produces consistent, searchable release histories.

The scope (optional, after type) identifies the affected area like 'auth' or 'database'. The body (wrapped at 72 characters) provides detailed explanation of the why and how. Together they create context that type and subject alone cannot convey.