Commit Messages
← Back to Writing for Engineers
Write in imperative mood (“Add feature” not “Added feature”). Follow conventional commits format (feat:, fix:, chore:). Explain why, not just what. A good commit history tells the story of how the codebase evolved.
Related
- Changelogs (derived from commits)
- Writing Good PRs (PR description supplements commits)