gac

Automating commit messages is the kind of task that sounds trivial until you read a year of bad ones, and this does it properly by understanding the diff rather than pattern-matching the path. The messages it produced were specific, correctly scoped, and followed conventional style without me asking twice. Where I would push further is configurability, since teams have strong and conflicting opinions about message format, and a project-level template would help. It also wants a fast path for trivial changes where a full model call is overkill. As a quiet quality-of-life tool it removed a small daily friction completely.

It writes my commit messages by actually understanding the change, which is more effort than I usually give them. The output was accurate and mercifully free of the word refactor. A flag to keep them short would suit my terse repos.

A commit message generator that actually reads the diff instead of guessing from filenames is a small thing that compounds across a thousand commits. It summarised a gnarly change accurately. I would like it to respect a repo's existing message conventions automatically.