Just Follow This for Git Commit Messages and Collaboration Gets Easier

Agreed—just adding a prefix makes git log actually enjoyable to read.

Hmm, I'd push back on that a bit. I've seen a few teams enforce prefixes, and all it did was add commits just to fit the format while the actual history got messier. And the "why" is better placed in the PR description than in the commit message—it's easier to search and doesn't interrupt the review flow. The idea that a single commit line can solve all collaboration seems a bit optimistic.

When our team first set conventions, we started by nailing down feat/fix, and it really paid off. In particular, if you can’t tell fix and chore apart, auto-generating release notes turns into a mess, and later you have to fix everything by hand lol. But for the one-line 'why,' don’t force it as a rule—it’s better to ask in review. When you force it, everyone just writes 'update.'