git-commit-formatter

To format a git commit message for Conventional Commits, structure it as <type>[optional scope]: description. This ensures your commit history remains consistent and generates actionable changelogs across your codebase.

A Conventional Commits message uses the structure <type>[optional scope]: description. You need a scope to target specific components within your software project, such as feature development, bug fixes, or documentation.

To add a BREAKING CHANGE footer to a conventional commit, the formatter validates your message and appends the footer when necessary to highlight breaking modifications in your code changes.

Yes, Conventional Commits validation helps with automated versioning by enforcing a standardized commit history. Teams use this standardized format to generate easier release notes and automate version bumps.

You can validate git commit messages for feature development, bug fixes, and documentation. The formatter checks the type, scope, and description to ensure they adhere to the Conventional Commits specification.