conventional-commits

Conventional commit messages enforce a structured format using types, scopes, and descriptions to produce a clean, machine-readable Git history. This structure clearly expresses the intent and scope of changes across software projects.

Standard conventional commit types include feat, fix, docs, and other maintenance task categories. These types define the purpose of your changes, providing clear rules and examples to assist in code reviews and automated tooling.

Apply scopes and bodies to conventional commit messages to describe changes by encapsulating structural context and detailed explanations. Scopes specify the affected area, while bodies provide additional context for code reviews.

You need conventional commits when teams require a clean, machine-readable Git history to solve inconsistent commit logs. They are applicable across software projects for features, fixes, docs, and maintenance tasks to promote consistency.

Conventional commits work with automated tooling by promoting consistency through a standardized message format. This machine-readable structure allows automated systems to parse features, fixes, and maintenance tasks accurately.

The best way to structure commit messages for code reviews is using conventional commits to enforce a clear format. Providing rules and examples for types and scopes helps reviewers understand the intent and scope of changes quickly.