Notes on Writing Good Commit Messages
gist.github.com
gist.github.com
Past tense ("Fixed ...") makes more sense when looking at a report of what was done.
2. Using the same tense as the todo list reduces rewriting.
i also sometime like to see a prefix indicating area like "GUI: blah" or "zfs: blah" so you can quickly categorize or get a sense for what area or subsystem was touched, if just looking at the messages and not the files changed.