3 ms·
This is why, if you have the agent generate the commit message at all, it has to be the same agent that wrote the code, in the same session. I usually have it
by miki123211 7d ago
This is why, if you have the agent generate the commit message at all, it has to be the same agent that wrote the code, in the same session.
I usually have it lead with a paragraph or two of context on why the change was made (though I often use it as just a tool to turn my rambling on that question into proper English), followed by a couple paragraphs of "abstract" explaining the change (because an LLM-generated summary reviewed by the person who made the commit is better than something which the person reading can get themselves).
- adastra22 6d agoI don't see how that would improve the situation? If I do it with the same agent/same context, it tends to just report what it did. Which is the diff, repeated in prose.
- miki123211 6d agoThe agent is usually told why it was making the change (I at least tend to start my prompts with a description of the problem we're solving), so, if prompted correctly, it can lead with "there was a bug, we root-caused it and here's what the root-cause was", then explain what the fix entailed.