I'm not sure if you already have a clear set of rules for how the commit messages should look like. But if you don't, I suggest we use the seven rules explained in this post which is probably the most widespread set of commit message rules.
Especially, I'm for using the imperative mood instead of the past tense (which you seem to apply), the main reason being this:
Git itself uses the imperative whenever it creates a commit on your behalf
Otherwise the history reads like sometimes imperative (like merge commits), sometimes past.
I'm not sure if you already have a clear set of rules for how the commit messages should look like. But if you don't, I suggest we use the seven rules explained in this post which is probably the most widespread set of commit message rules.
Especially, I'm for using the imperative mood instead of the past tense (which you seem to apply), the main reason being this:
Otherwise the history reads like sometimes imperative (like merge commits), sometimes past.