I would recommend to also look at this guideline + tooling to create an automatic changelog based on your commits: https://www.conventionalcommits.org/
I always force myself to write good commit message.
But I often ask myself if it is really useful or if I'm just too tight and want things to look good.
This standard might be useful for library maintainers in the cases stated here: https://www.conventionalcommits.org/en/v1.0.0-beta.2/#why-us...
Like having everyone using the same guidelines (code style) when writing code. This might also be useful if everyone use it.