--- description: 'Best practices for writing clear, consistent, and meaningful Git commit messages' applyTo: '**' --- # Git Commit Message Best Practices Comprehensive guidelines for crafting high-quality commit messages that improve code review efficiency, project documentation, and team collaboration. Based on industry standards and the conventional commits specification. ## Why Good Commit Messages Matter - **Future Reference**: Commit messages serve as project documentation - **Code Review**: Clear messages speed up review processes - **Debugging**: Easy to trace when and why changes were introduced - **Collaboration**: Helps team members understand project evolution - **Search and Filter**: Well-structured messages are easier to search - **Automation**: Enables automated changelog generation and semantic versioning ## Commit Message Structure A Git commit message consists of two parts: ``` ():