commit-message

A standard git commit message uses a capitalized type such as Feature, Fix, or Refactor, followed by a concise imperative summary. You can add an optional body to explain the rationale and impact of the changes before pushing.

The correct git commit subject line structure uses a capitalized type, such as Docs or Build, followed by a concise imperative summary. This pattern ensures the commit message clearly identifies the change category and action.

You need to include a body in your git commit message when you must explain changes, rationale, and impact beyond the subject line. It provides context for feature development, bug fixes, or documentation updates across the repository.

To verify a commit message, draft it following the Type: Short Summary pattern and review it against the staged diff. This validation process ensures the message accurately reflects the repository changes before you push the commits.

For bug fixes and feature development, use the capitalized types Fix and Feature respectively. Other supported types include Refactor, Test, Docs, and Build to categorize repository changes according to workflow rules.