No amount of good tooling can compensate for bad reasoning. Good commit messages are ones that fit in how the team/organization handle versioning so work can be

No amount of good tooling can compensate for bad reasoning. Good commit messages are ones that fit in how the team/organization handle versioning so work can be parceled and context recovered with minimal cognitive load for all parties involved. Shoving another vendor in the chain because the demo looks great is a sign reasoning is not so great. This kind of layering poorly though out fixes is how most mudballs I've encountered have grown.