git-commit-formatter

To format git commit messages using conventional commits, structure your message with a type like feat or fix, an optional scope in parentheses, and an imperative description, such as `feat(auth): add password reset functionality`.

The conventional commits specification standardizes git history by enforcing commit types like feat or fix, optional scopes, and imperative descriptions, which improves clarity and enables automated changelog generation.

To indicate a breaking change in a conventional commit, add a `BREAKING CHANGE:` footer to your commit message, which clearly identifies backward-incompatible modifications in your version control history.

The best way to structure a git commit message for a bug fix is to use the `fix` type followed by an optional scope and an imperative description, such as `fix(payment): resolve transaction timeout error`.

You need to use conventional commits in version control when you want to ensure commit history clarity, structure changes consistently, and enable automated changelog generation directly from your git messages.