Skip to content

The Good Commit Message

Easy — everyone uses thisGeneral Dev

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."

Made with passive-aggressive love by manoga.digital. Powered by Claude.