How to Write Good Get Commit Messages

The software industry changes every 12 minutes, so what used to be a best practice can easily fall out of fashion or no longer be relevant. You have to anchor to the why of the thing instead of just saying one must do TDD and one must do good get commit messages. It's like, yeah, but like, but why though? What's the benefit? Let's make sure that we're clear on the benefit.