Commit Messages

Semantic commit messages for traceability

Conventional commits provide structured messages that enable automated changelog generation and maintain clear project history.

Why Conventional Commits?

Semantic commit messages enable:

Automated changelog generation - Tools can extract features, fixes, and breaking changes
Clear project history - Anyone can understand what changed and why
Semantic versioning - Commit types inform version bumps (feat = minor, fix = patch)
Traceability - Link commits to issues and requirements

<type>(<scope>): <description>

[optional body]

[optional footer]

Key Types: feat, fix, docs, style, refactor, test, chore

You are here: Explanation — understanding-oriented discussion that clarifies concepts.