Ask HN: Do solo indie devs write commit messages?
I don't do this and don't feel like I am missing much...
The audience for commit history is different than for release notes. So for example, you might fix a race condition for a specific situation and during debug, notice that there might be another related race condition (but maybe you're not sure it could actually happen). A comment about that in the commit log might be helpful down the road if that other race condition occurs later.
You can squash commits and their messages into one merge, which could achieve the same result.
But I find creating a branch per feature is really great way to work. Even if it's just you.