fix(review): AI review lanes report success without posting a review on large PRs
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 45/100
调研方向
Start by locating the Claude review and security review lane workflows, then trace how each lane records completion and writes the “reviewed through” marker. Reproduce the large pull request behavior described for #7009 and inspect how diff retrieval handles GitHub’s 300-file cap. Done means incomplete lanes report failure or neutral and omit the marker, with full diff coverage or a summary that identifies partial coverage.
由索引模型根据 Issue 内容生成。
描述
Problem
On a large pull request, both AI review lanes conclude success without posting any review.
Observed on #7009 (828 changed files, head 55236cd59; runs 38179498349 and 38179498378, both success):
- claude-review: the sticky progress comment stopped with 2 of 8 checklist items ticked. "Verify candidate findings, post inline comments" and "Final summary" were never reached. The comment says
gh pr diff/gh apihit GitHub's 300-file diff cap and git fetch had no network, so the review covered only the 100 files supplied in context. No inline comments or review were posted. - claude-security-review: the sticky comment stopped at "Fan out 4 hunters ... running". "Adversarially verify" and "Post findings" were never ticked. No findings were posted.
- Both posted a "reviewed through " marker anyway.
A green check row therefore claims a review that did not happen.
Expected
- A lane that does not reach its post or summary step concludes as failure or neutral, not success, and does not write the "reviewed through" marker.
- claude-review gets the full diff without the 300-file API cap (for example a local
git diffagainst a fetched base), or says in its summary that coverage was partial and which files it skipped.
- 主要语言
- Shell
- 星标
- 22
- 派生
- 2
- 平均合并
- 8 小时 24 分钟
- 30 天内合并 PR
- 947
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
melodic-software/claude-code-plugins 的其他 Issue
-
needs-human needs-triage priority: medium
难度 2/5 1-3 小时 新手友好度 65/100
melodic-software/claude-code-plugins#7455 · 1 条评论 ·
维护者通常 1 天内回复
-
priority: medium
难度 2/5 1-3 小时 新手友好度 68/100
melodic-software/claude-code-plugins#7351 · 2 条评论 ·
维护者通常 1 天内回复
-
agent-ready priority: high work-class: scoped
难度 2/5 1-3 小时 新手友好度 74/100
melodic-software/claude-code-plugins#7312 · 3 条评论 ·
维护者通常 1 天内回复
-
priority: medium
难度 2/5 1-3 小时 新手友好度 76/100
melodic-software/claude-code-plugins#7288 · 2 条评论 ·
维护者通常 1 天内回复
-
knowledge: docpage-digest dual verification defines no verdict vocabulary or pass/fail threshold未关闭needs-human
难度 2/5 1-3 小时 新手友好度 78/100
melodic-software/claude-code-plugins#7286 · 2 条评论 ·
维护者通常 1 天内回复
查看 melodic-software/claude-code-plugins 的全部 Issue
相似的 Issue
-
bug needs-triage
难度 1/5 1 小时以内 新手友好度 78/100
mattpocock/skills#1281 ·
维护者通常 1 天内回复
-
github_actions
难度 2/5 1-3 小时 新手友好度 62/100
hiero-ledger/hiero-consensus-node#27621 ·
维护者通常 1 天内回复
-
application-issue
难度 2/5 1-3 小时 新手友好度 72/100
Installomator/Installomator#3427 ·
维护者通常 3 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
software-mansion/argent#1483 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 62/100