commit-convention

Format git commit messages using the type(scope): subject syntax to ensure a clean, atomic history. This standard applies to features, fixes, and docs, clarifying the change intent and domain boundaries for easier tracking and rollback.

An atomic commit includes a single logical change, simplifying rollback and tracking. You need atomic commits in version control to reduce inconsistencies and omissions, ensuring a clean project history and streamlined change log management.

Include breaking changes and linked issues in a commit message by using the correct footer. This ensures the project history records critical updates and issue resolutions accurately alongside the standard type(scope): subject syntax.

Conventional commits work for the majority of project changes including new features, fixes, and docs. By applying type(scope): subject syntax, it standardizes the change log and maintains consistent version-control history across different domains.

The best way to write a commit message body for code review is to include the change reason and detailed information when needed. This body rule complements the atomic commit and standard subject line, promoting clearer code reviews.