Committing with Intention: The Art of a Good Commit

Part 2 of the Git Mastery Series ← Part 1: How Git Actually Thinks | Part 3: Branching Without Fear → Six months into a project, you're hunting a bug. You run git log and the history looks like this: a3f8c9d fix 1b4e7a2 update c5d2f8a wip 9d3e1f4 asdf 7a2b5c8 final 4f1e8d6 final2 2c9a3b7 ok now it works Who wrote this? You did. And now you have no idea what any of these commits contain without opening each one individually. Compare that to this: a3f8c9d fix(auth): handle expired JWT tokens on refresh 1b4e7a2 feat(cart): add quantity update on product page c5d2f8a refactor(api): extract payment service into dedicated class 9d3e1f4 fix(checkout): prevent duplicate order on double-click submit Same code. Same history. The second version is documentation. The first is noise. The commit isn't just a save point. It's a message to the next person reading this code — which is almost always future you. What an Atomic Commit Actually Means "Atomic commit" is one of those terms that gets thrown a