commitizen

"refactor: changed stdout statements" is a useless commit message. I should not have to manually open the commit to find out what was actually changed. The message should specify changed X to a. If it's too long, that's what the git commit description is for. The keywords are also redundant. I don't need to see doc) if the rest of the commit message reads "update README". That's obviously documentation. "style: black to files" ??? all that was changed was styling here with newlines and quotes. [0] --- To be frank, it's not that hard to write a good commit message. It just requires you to use your brain for more than .2 seconds to write a good, concise summary. Forcing yourself to do this also in turn makes you write better (concise, focused) commits instead of just shutting off your brain and following some tool. [0]: https://github.com/W

I prefer conventional commits, I have created a tool that prompts some info to make it easier to remember, I can also bump automatically the version using the commits. I've been using it with friends with no issues. I really like how the commit log looks https://github.com/Woile/commitizen