git-commit

To enforce conventional commit messages in git, validate commit types, subject length, and imperative mood against the Conventional Commits specification, ensuring concise subjects limited to 50 characters and valid types like feat, fix, or docs.

The conventional commit format for a bug fix uses the type fix followed by an optional scope and a concise imperative subject, such as fix(auth): resolve login timeout, to maintain clear version control history.

You need to use conventional commits during feature development, bug fixes, documentation updates, and refactors to maintain a consistent git history and generate easier release notes across the codebase.

Yes, the conventional commit specification limits subject lines to 50 characters, requiring concise, imperative mood phrasing to standardize change narration and satisfy the format validation.

Yes, you can include optional footer references in conventional commit messages alongside a brief body, allowing you to link issues or breaking changes while satisfying the Conventional Commits specification.

Valid commit types for conventional commits include feat, fix, docs, style, refactor, perf, test, build, ci, chore, and revert, ensuring standardized version control narration across various development workflows.