git-commits

Conventional commit messages use structured formats with type prefixes like feat or fix, imperative mood summaries under 50 characters, and detailed bodies wrapped at 72 characters to clarify code changes. Templates and examples enforce this consistency across software projects.

The best way to format a git commit body is to wrap text at 72 characters, structure details logically, and document changes thoroughly. Following these best practices reduces ambiguity and friction during code reviews.

Imperative mood in git commits matches how git generates default messages and keeps summaries concise. This Skill enforces imperative mood for one-line summaries under 50 characters, ensuring clarity and consistency across version control history.

Yes, this approach includes test-before-commit guidance as part of its best practices. It provides structured rules for verifying changes and documenting tests thoroughly within commit messages before finalizing version control updates.

Use conventional commit templates to document common scenarios by applying structured formats with type prefixes and detailed bodies. The Skill provides examples that enforce proper message formatting, length rules, and thorough documentation of changes for each specific case.

Yes, this approach applies across software projects to enforce conventional commits, proper message formatting, and thorough documentation. It provides universal rules for message length, imperative mood, and body wrapping regardless of the specific repository.