If the wording of the commit message is the issue, there are ways to reduce the toil without having AI confabulate a message. Conventional Commits <https://www.

If the wording of the commit message is the issue, there are ways to reduce the toil without having AI confabulate a message. Conventional Commits <https://www.conventionalcommits.org/en/v1.0.0/ https://www.conventionalcommits.org/en/v1.0.0/> has been discussed on HN many times. The 50/72 practice (some tools will help with this) <https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html https://tbaggery.com/2008/04/19/a-note-about-git-commit-mess...> and many many words out there suggesting some best practices. A team can and should work out their own best practices. A git prepare-commit-msg hook can provide a template for message conventions. Perhaps there's room for a tool or UI enhancement to provide additional guidance.