Git commits are so simple that it is easy to do it bad. When you try to figure out a codebase, it really doesn't help that you have a Git history filled with messages like "testing", "fix bug", or even obscure messages where you just mashed your hands on your keyboard to type out "asdasd".

What if I told you that others struggled with this enough to create a specification for commit messages? A system to the madness, so to speak. A tool that promotes better readability, makes it easier to collaborate, and enables automation of all those boring chores you have to do before release.

In this talk we will be looking at Conventional Commits. It is easy to adopt, simple to implement, and powerful in its impact. Say goodbye to "mystery meat" commit messages, and welcome a system that works for you, not against you. You'll thank me later.