conventional-commit

To write a conventional commit message, enforce the header format <type>[optional scope]: <description>. Keep descriptions imperative and concise, using types like feature, fix, docs, or chore to ensure consistent changelogs and semantic clarity.

The conventional commits format for semantic PR titles requires the structure <type>[optional scope]: <description>. This standardizes code review and git workflow by keeping titles imperative, concise, and categorically typed for easier automation.

You can validate existing commit messages by checking them against the canonical conventional commits specification. The validation process enforces the header format and surfaces corrected options when messages do not comply with repo-local guidelines.

Yes, you can rewrite non-conforming git commit messages to follow the standard. The process suggests appropriate type and scope based on code changes, applying the <type>[optional scope]: <description> format to update feature, fix, docs, and chore commits.

Yes, this conventional commit linter supports repo-local guidelines for code review. It checks commit messages and semantic PR titles against repository-specific rules, enforcing the header format and providing corrected options for non-compliant entries.

Limitations of enforcing conventional commit messages involve strictly adhering to the <type>[optional scope]: <description> header format. Messages must remain imperative and concise, and non-conforming updates require rewriting to pass semantic PR title checks and repo-local validation.