"comments -> agent" flow
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 775
- Forks
- 57
- PR merge metrics
- No merged PRs in 30d
Description
`/diffity-resolve uses full diff context while "Copy comments" uses scoped comment context, causing large-prompt regressions
In the UI, the Copy comments button appears to produce a relatively small, comment-scoped payload.
By contrast, running /diffity-resolve seems to pull in the entire active diff, even when there are only a small number of unresolved comments. On large diffs, this makes the resolve flow much heavier and less focused than the copied-comments path.
Expected behavior
/diffity-resolve should default to a comment-scoped context, similar to the UI copy flow
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the /diffity-resolve flow and compare how it builds context with the UI's Copy comments path. Confirm where the active diff is added and how unresolved comments are selected. Done means /diffity-resolve defaults to the same comment-scoped context without including the full active diff.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100