I still follow my past team definition of a good commit : the commit message should answer in it's first line why this commit was done. Overtime I realized that

I still follow my past team definition of a good commit : the commit message should answer in it's first line why this commit was done. Overtime I realized that when I git blame I never care what a commit does because this is always obvious by reading the code of the commit. The reason why, however, is most of the time not obvious at all.