The Only Good Commit Message Is a Clear One

A useful commit message tells me why a change exists. I can already see the files it touched.

"Fix navigation" leaves a lot to rediscover. "Keep the menu open when focus moves between links" gives the next reader a behaviour to check. If the reason needs more space, put it in the body. This doesn't require an essay on every commit, just enough context that someone investigating a regression can recognise the relevant change.