[{"data":1,"prerenderedAt":78},["ShallowReactive",2],{"term-t\u002Fthe-good-commit-message":3,"related-t\u002Fthe-good-commit-message":60},{"id":4,"title":5,"acronym":6,"body":7,"category":40,"description":41,"difficulty":42,"extension":43,"letter":44,"meta":45,"navigation":46,"path":47,"related":48,"seo":54,"sitemap":55,"stem":58,"subcategory":6,"__hash__":59},"terms\u002Fterms\u002Ft\u002Fthe-good-commit-message.md","The Good Commit Message",null,{"type":8,"value":9,"toc":33},"minimark",[10,15,19,23,26,30],[11,12,14],"h2",{"id":13},"eli5-the-vibe-check","ELI5 - The Vibe Check",[16,17,18],"p",{},"'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.",[11,20,22],{"id":21},"real-talk","Real Talk",[16,24,25],{},"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.",[11,27,29],{"id":28},"when-youll-hear-this","When You'll Hear This",[16,31,32],{},"\"Whoever wrote 'fix stuff' as a commit message, please, for the love of god, write a real one.\" \u002F \"That was a genuinely good commit message, I understood the whole incident from the diff alone.\"",{"title":34,"searchDepth":35,"depth":35,"links":36},"",2,[37,38,39],{"id":13,"depth":35,"text":14},{"id":21,"depth":35,"text":22},{"id":28,"depth":35,"text":29},"general","'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.","beginner","md","t",{},true,"\u002Fterms\u002Ft\u002Fthe-good-commit-message",[49,50,51,52,53],"Commit","Conventional Commits","Git Blame Driven Development","Documentation","Squash",{"title":5,"description":41},{"changefreq":56,"priority":57},"weekly",0.7,"terms\u002Ft\u002Fthe-good-commit-message","DQr2Tal8j9A7_gkCpxzVw5Tx9dyN59GKzqBjZ9NVqqo",[61,65,68,71,74],{"title":49,"path":62,"acronym":6,"category":63,"difficulty":42,"description":64},"\u002Fterms\u002Fc\u002Fcommit","git","A commit is like pressing the save button in a video game.",{"title":50,"path":66,"acronym":6,"category":63,"difficulty":42,"description":67},"\u002Fterms\u002Fc\u002Fconventional-commits","Conventional Commits is a format for writing commit messages that humans AND machines can understand.",{"title":52,"path":69,"acronym":6,"category":40,"difficulty":42,"description":70},"\u002Fterms\u002Fd\u002Fdocumentation","Documentation is written explanation of how your code works and why.",{"title":51,"path":72,"acronym":6,"category":63,"difficulty":42,"description":73},"\u002Fterms\u002Fg\u002Fgit-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.",{"title":53,"path":75,"acronym":6,"category":63,"difficulty":76,"description":77},"\u002Fterms\u002Fs\u002Fsquash","intermediate","Squash is like combining multiple save points into one.",1792528130500]