I don't think it is important that everyone on the team has the exactly same style, however you should discuss some minimum requirements for a quality commit message, and make sure that during code review (ideally before merging a PR) the message meets the requirements.
I use the following style:
<imperative present-tense verb> <description> (<issue#>)
For example:
fix mobile breakpoint on iOS 8 iPad Air (#12345)implement new side-bar layout (#54321)remove unused code (#99999)Following the thinking that a commit applies a patch (to the history), and the comment is a label for the action, it allows a quick understanding when checking the git history, and also references the issue for a more detailed description of the changes. The rest is my personal taste.