The Good Commit Message
ELI5 - The Vibe Check
'fix stuff' tells you nothing. 'Fix race condition in payment webhook retry logic, see incident #4521' tells you everything, six months from now, at 2 a.m., when you're trying to understand why this line exists. The good commit message is a small act of kindness to a future teammate, who is probably you, who has completely forgotten writing this code.
Real Talk
A good commit message clearly explains the reasoning and context behind a change, not just a restatement of what the diff already shows, following conventions like a concise summary line and an explanatory body for non-trivial changes. It pays off disproportionately during debugging, git blame investigations, and onboarding, when the reasoning behind a change matters far more than the change itself.
When You'll Hear This
"Whoever wrote 'fix stuff' as a commit message, please, for the love of god, write a real one." / "That was a genuinely good commit message, I understood the whole incident from the diff alone."
Related Terms
Commit
A commit is like pressing the save button in a video game.
Conventional Commits
Conventional Commits is a format for writing commit messages that humans AND machines can understand.
Documentation
Documentation is written explanation of how your code works and why.
Git Blame Driven Development
Git blame driven development is when you look at broken code and your first action isn't to fix it — it's to run `git blame` to find out who wrote it.
Squash
Squash is like combining multiple save points into one.