Adopt a convention like commitizen: https://github.com/commitizen/cz-cli

'typeofchange(scopeofchange): reason for change'

It sort helps force devs to type out more meaningful commit messages.

That will not necessarily make aider write better commit messages (unless I possibly tell it explicitly why I am doing something in every instruction).