* Why standardize messages? Its clean. Easy to see what changed and when. As an up-and-coming developer, my repos will probably be potential employers first impressions of me. Clean code (proper indentions/spacing etc) and formatted commit messages help show that I care about my code.
* The workflow is to create a `.txt` file as a template, and configure git to use that file as the default message when commiting.
* The key is the character count. Note the dashed lines representing 50 characters for the summary, and 72 for the description.