Commit messages should explain intent
A useful commit message answers what changed and why at a high level. Consistent wording makes history easier to scan and can support automated release tooling.
A common structured format
A Conventional Commits style message uses a type such as feat, fix, docs, refactor, test or chore, followed by a concise description. Teams can add scopes and breaking-change information if their release process uses them.
Do not write implementation diaries
A commit message should not list every line changed. The diff already shows implementation details. The message should provide durable context about the purpose of the change.
ADVERTISEMENT