This is just polishing bad commit messages, it doesn't make them better.
A commit message should tell you why the code changed, not summarize what changed. I can read a code change and see what it does, but I can only guess what caused that change to be made unless the message tells me what was in your head (unless it's a trivial commit like a typo fix)
It makes them better, up to a point. Many commits (esp in private repos or WIP branches) are barely descriptive and of the form "stuff broke" "i got test to pass" "yay", etc. These commits don't make it into mainline, and I don't really want to spend time carefully writing them. In this case, a tool like this may be useful.
Also, the `aicommit` tool has a -c flag for accepting context and the "why". I have only been playing with it for a couple of days so I'm not sure how effective it will be.
Comments
This is just polishing bad commit messages, it doesn't make them better.
A commit message should tell you why the code changed, not summarize what changed. I can read a code change and see what it does, but I can only guess what caused that change to be made unless the message tells me what was in your head (unless it's a trivial commit like a typo fix)
See eg https://cbea.ms/git-commit/#why-not-how for a longer discussion.
It makes them better, up to a point. Many commits (esp in private repos or WIP branches) are barely descriptive and of the form "stuff broke" "i got test to pass" "yay", etc. These commits don't make it into mainline, and I don't really want to spend time carefully writing them. In this case, a tool like this may be useful.
Also, the `aicommit` tool has a -c flag for accepting context and the "why". I have only been playing with it for a couple of days so I'm not sure how effective it will be.