git-commit-formatter

Formatting git commit messages involves applying a type-based convention to staged changes. The formatter selects a dominant type from a table (fea, fix, ref, ai, test, oth), enforces lowercase, and writes an imperative-mood description under 72 characters.

The conventional format for git commit messages is a structured syntax: type(optional scope): description. It uses simplified types like fea, fix, ref, ai, test, or oth to keep project history concise and consistent across development workflows.

You indicate a breaking change in a conventional commit message by appending a BREAKING CHANGE footer. The formatter adds this footer when you specify that the staged development work introduces backward-incompatible modifications.

Yes, the commit formatter supports adding a scope to the commit type. It encourages including a scope when it clarifies which component changed, generating scope-aware descriptions that improve readability in project history.

The character limit for the first line of a git commit message is 72 characters. The formatter enforces this constraint while ensuring the description uses lowercase formatting and imperative-mood phrasing for structured consistency.

You need to use a type-based convention for git commits when you want to solve the problem of inconsistent, unclear project history. It turns staged development work into short, structured messages that fit a shared team convention.