commit-message

A conventional commit message requires a type prefix such as feat, fix, or chore, followed by a concise lowercase subject under 72 characters. This standardizes git history and improves readability during code reviews.

A git commit message body should include a what and why rationale behind the changes. Explaining what changed and why it was necessary ensures every commit is easy to understand when navigating project history.

Yes, the commit message template requires an annotated project file tree section. Including the file tree provides necessary context directly in the message, helping collaborators understand exactly which files were modified.

The character limit for a conventional commit subject line is under 72 characters. Keeping the subject concise and lowercase ensures compatibility with standard git linting workflows and improves history readability.

You need to use conventional commits in your git workflow when collaborating on software projects to ensure standardized history. Enforcing this structure improves changelog clarity and makes commits easy to understand during reviews.

Valid type prefixes for conventional commit messages include feat, fix, chore, refactor, docs, and test. Applying these prefixes categorizes changes consistently across the project's git history.