skill-pr-addresser: Improve feedback deduplication and batching
@aRustyDev is already working on this.
Since Jan 2, 2026.
Assessment
This issue has not been assessed yet.
Description
Problem
The agent times out when processing PRs with many review comments because:
- No deduplication of similar feedback - "Move to examples" appearing at 4 different lines creates 4 separate work items
- Guidance mixed with actionable items - Meta-guidance reviews (e.g., "follow progressive delivery patterns") are treated as change requests
- Checkbox explosion - A single review with 6 checkboxes becomes 6 separate items
- No batching - All items processed in a single fixer run
Example from PR #795
| Source | Items Generated |
|---|---|
| Review 1 (6 checkboxes) | 6 items |
| Review 2 (guidance) | 1 item |
| Review 3 (guidance) | 1 item |
| 11 review threads | 11 items |
| Total | ~17-20 items |
Many threads are actually the same feedback at different locations:
- 4 threads say "move to examples/*"
- 3 threads say "move to reference/*.md"
- 3 threads say "keep high-level, point to references"
Proposed Solutions
1. Deduplication in Analyzer
Update feedback-analyzer prompt to consolidate similar feedback:
{
"feedback_items": [
{
"id": "group-examples",
"type": "change_request",
"description": "Move code blocks to examples/",
"locations": [
{"file": "SKILL.md", "line": 671},
{"file": "SKILL.md", "line": 733},
{"file": "SKILL.md", "line": 398}
],
"priority": "high"
}
]
}
2. Separate Guidance from Actions
Add a guidance type that the fixer can use for context but not treat as individual work items:
{
"guidance": [
"SKILL.md MUST follow progressive delivery patterns",
"Adopt best-practices & anti-patterns pattern"
],
"feedback_items": [...]
}
3. Batch Processing
Instead of sending all items to fixer at once:
- Group by type (move-to-examples, move-to-references, etc.)
- Process one group at a time
- Commit after each batch
4. Priority Ordering
Process high-priority items first, skip lower priority if time/turn budget exhausted.
Related
- #796 - Detect updated comments
- Observed in PR #795 (10 items all timed out)
- Dominant language
- Jupyter Notebook
- Stars
- 8
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Contributor guide
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.
More from aRustyDev/agents
-
dependencies github-actions
Difficulty 1/5 Under an hour Newbie friendliness 72/100
-
dependencies github-actions
Difficulty 3/5 1-2 days Newbie friendliness 25/100
-
dependencies github-actions
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
-
dependencies github-actions
Difficulty 1/5 Under an hour Newbie friendliness 25/100
-
dependencies github-actions
Difficulty 1/5 1-3 hours Newbie friendliness 45/100