conventional-commits

Enforce conventional commit messages by validating the <type>(<scope>): <subject> pattern during commit creation. This verifies allowed types like feat, fix, and docs, and can integrate with git hooks or CI to block non-conforming commits.

Allowed conventional commit types include feat, fix, docs, style, refactor, test, chore, build, ci, perf, and revert. The validation checks the message format against these specific types to ensure structured git history.

Use conventional commits in CI to generate changelogs and improve release planning. The structured <type>(<scope>): <subject> format allows automated changelog generation by hooking the validation into your CI pipeline.

Fix invalid conventional commit formatting by following automated guidance suggestions. The validation enforces subject length and formatting rules, prompting corrections to ensure the message matches the required <type>(<scope>): <subject> pattern.

Enforce structured commit messages for code review to improve git history readability and automate changelog generation. Validating the conventional commits specification ensures consistent type, scope, and subject formatting across all project commits.