hs-git-commit-messages

To enforce a standard git commit message format, draft messages that follow the repository's subject and body structure, inferring TYPE and TICKET where unambiguous and prompting for clarification when missing. This ensures consistent, searchable history and streamlines code reviews.

Commit message validation workflows can prevent inventing ticket numbers by enforcing subject and body structure and prompting for clarification when ticket information is missing. This guarantees ticket numbers are never fabricated and commit history remains accurate.

The best way to write git commit messages and PR descriptions for team reviews is to apply the repository's standard conventions across both, providing a clear subject and a concise body that infers TYPE and TICKET where unambiguous to maintain consistency.

Commit message format validation fails when a ticket number is missing because the workflow prompts for clarification rather than inferring or inventing the ticket. This strict enforcement ensures traceable history and prevents false ticket associations.

You need a repository standard to generate commit messages and PR descriptions because the workflow enforces defined subject and body conventions, inferring TYPE and TICKET based on the existing rules to maintain a consistent and searchable history.