Let me be honest: the perfect message does not exist. If you work alone, you probably find the best way for you, but when in a team there are different minds and different sensibilities, so what is good for me might not be as good for somebody else.

In this case you have to sit down around a table and make a retrospective, trying to end up with a shared standard; it may not be the one you prefer, but at least it's a way to find a common path.

Rules for a good commit message really depend on the way you and your team work day by day, but some common hints can be applied by everyone; here they are.