But that's not how git itself makes commit messages: (`Merge branch 'foo'`, `Revert 'some thing'`) Not every commit changes how the code works. Some is just do

But that's not how git itself makes commit messages: (`Merge branch 'foo'`, `Revert 'some thing'`) Not every commit changes how the code works. Some is just documentation-related, or formatting, or some other configuration change. The list goes on. Your approach would only make sense in a subset of cases. IMO the message should be what the commit does, not what the code does.