conventional-commit

Standardize git commit messages by applying Conventional Commits rules for type, scope, and breaking changes to enable automated release notes and changelog generation across multiple repositories.

The conventional commit format for a breaking change requires a specific type, an optional scope, and a clear breaking change indicator in the message body to document the modification accurately.

Write a multi-line commit body for a feature fix by using the conventional commit type 'fix', adding an optional scope, and following practical examples to ensure traceability and proper documentation.

You can use conventional commit linting to enforce standardized type and scope rules across multiple repositories, ensuring project history remains readable and easy to audit for all team members.

Conventional commit linting enforces specific rules for description length, type, scope, and multi-line bodies, ensuring that commit messages fit development workflows and maintain traceability.