3 ms·
Hmm. All of the examples simply describe what the code is doing. I need a tool that explains the intent and context behind a change.
by SkyPuncher 6mo ago
Hmm. All of the examples simply describe what the code is doing. I need a tool that explains the intent and context behind a change.
- munksbeer 6mo agoExactly. "Why was this change made"? "What were the options"? "Why this is a good way of doing it"? "What are the subtle things I came across while making this change"?
- cpan22 6mo agoYep that's something we're actively working on! would love to hear any perspectives on best ways to approach this
- stackskipton 6mo agoThere isn't one. Most of time you would pair review a PR with human who wrote it and they could explain that. They can't anymore since 9/10, they didn't think through those things.
- viktorianer 6mo ago[dead]
- lbreakjai 6mo agoIf you've worked from a plan, it's trivial. I've got a setup where the agent reads the implementation plan, then creates a commit history based on intent rather than location.