Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

skill-pr-addresser: Improve feedback deduplication and batching

Aperta
#797 0 commenti 0 reazioni 1 assegnatario Vedi su GitHub

@aRustyDev ci sta già lavorando.

Dal 2/1/2026.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

agents enhancement skills

Problem

The agent times out when processing PRs with many review comments because:

  1. No deduplication of similar feedback - "Move to examples" appearing at 4 different lines creates 4 separate work items
  2. Guidance mixed with actionable items - Meta-guidance reviews (e.g., "follow progressive delivery patterns") are treated as change requests
  3. Checkbox explosion - A single review with 6 checkboxes becomes 6 separate items
  4. 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:

  1. Group by type (move-to-examples, move-to-references, etc.)
  2. Process one group at a time
  3. 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)
Lingua principale
Jupyter Notebook
Stelle
8
Fork
3
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Guida per i contributori

Apri la guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di aRustyDev/agents

Tutte le issue di aRustyDev/agents

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.