See how a small change in the style of your commit message can make you a better programmer using the semantic commit convention in GIT:
build - Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
ci - Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
docs - Documentation only changes
feat - A new feature
fix - A bug fix
perf - A code change that improves performance
refactor - A code change that neither fixes a bug nor adds a feature
style - Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
test - Adding missing tests or correcting existing tests
feat: add hat wobble
^---^ ^------------^
| |
| +-> Summary in present tense.
|
+-------> Type: chore, docs, feat, fix, refactor, style, or test.