git-commit

To write a Conventional Commit message, use the format type(scope): description with an imperative subject line, a body wrapped at 72 characters, and footers for issue references or breaking changes to keep Go history atomic.

The correct conventional commit structure uses a type like feat or fix, followed by an optional scope in parentheses, a colon, and an imperative description, optionally adding a wrapped body and footers for breaking changes or issue references.

To keep git history atomic for interactive rebases, ensure each single-purpose commit builds and tests independently, uses imperative conventional commit subjects, and includes relevant package scopes and issue footers for easy reversion.

Yes, the pre-commit workflow recommends running formatting, linting, building, and testing before committing changes to verify they pass independently and avoid pushing broken commits into your repository history.

To indicate a breaking change in a conventional commit message, add a footer starting with BREAKING CHANGE: describing the modification, or append an exclamation mark after the type and scope before the colon.

Wrapping the conventional commit body at 72 characters ensures the message displays correctly in terminal windows and git log outputs without awkward line breaks, maintaining readability for structured atomic history.