I disagree. Good commit messages also document the product. They should describe or reference features requested, bug reported, and the _why_ of the change at

I disagree. Good commit messages also document the product. They should describe or reference features requested, bug reported, and the _why_ of the change at least as much as the _what_ of the change.