Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

skill-pr-addresser: Improve feedback deduplication and batching

未关闭
#797 0 条评论 0 个 reaction 已指派 1 人 在 GitHub 查看

@aRustyDev 已经在做这个了。

开始于 2026年1月2日。

评估

这个 Issue 还没有评估数据。

描述

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)
主要语言
Jupyter Notebook
星标
8
派生
3
PR 合并指标
30 天内没有已合并 PR

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

aRustyDev/agents 的其他 Issue

查看 aRustyDev/agents 的全部 Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。