[lowercased]

> and I keep running into people wishing developers spent more time writing better commit messages.

that's not at odds with what the GP posted.

I've worked in places where people spent a lot of time and effort 'improving' commit messages - reviews on those, rewriting, meetings, etc. after several months, the 'team' such as it was was writing 'better' messages per the few people who made the determination as to what 'better' was. they were the people who made it a focus and said this was necessary.

bug reports didn't go down. time to turn around functionality and fixes didn't go down. code review time didn't really go down. we didn't get more code coverage. code didn't execute faster. no one we delivered business value to was happier, or got more value. not in the immediate moment these changes took place, nor in the months that followed.