Quickly check and format a commit message's top line (help information).
- Log command output indent
- Maximum line length
- Prefix
- Suffix
Information
In Test-driven Development there are three types of commits:
"red" after a failing test/part-test;
"green" when that test/part passes and
"refactor" when changes are made to improve the code's quality along the lines of DRY, the single responsibility principle and other such guidelines.
Commits should alternate between "red" and "green", with optional refactorings after a "green" commit.
It helps, particularly when performing a Test-driven Development kata, for the commit messages to tell a story (and, for katas, to be only one line, so they can be quickly read). This tool makes it easy to format them into sentences.
Note: "green" commits do not need messages, as their purpose should be clear from the preceeding "red" commit.
There was some interesting information in this StackOverflow question and answers on git commit message formatting.