PR Review — AI Agent Review for one pull request

Repo profile — read .claude/repo-profile.md first. This skill is repo-agnostic; arc is the reference implementation. Use the profile's values wherever this doc shows an arc default: repo_slug (the gh -R target), gate_mode (arc = scripts: no CI on PRs, so gh pr checks is empty and the verification scripts are the only gate; ci/both repos ALSO fold in gh pr checks), verification_entry / pre_merge_entry. Arc's own provenance for the lessons below is not inlined here (fuller case narratives, where they exist, are under .claude/case-law/).

把一个 PR 处理到位:读 PR diff + 关联 issue + 已有 review/comments → 对照已落地代码/测试逐条核验 → 跑 verification 门控(pre-merge)并判读根因(PR 上已无 CI) → 检测与兄弟 PR 的冲突/重复 → 产出带证据的合并就绪判定,落回 PR(comment),而不是埋在某次对话里。

这是 issue-review 的 PR 版:同一台引擎(读 → 对照现实 → 带证据落 comment),对象换成 PR,多了三件 issue-review 没有的事——跑 verification 门控并判读、跨 PR 冲突检测、合并就绪判定。

输出语言与写作规范 = profile comment_language。 verdict comment、「需人确认块」等一切面向团队的产出一律用该语言写叙述(团队阅读语言);代码标识符、路径、命令、path:line、gh 输出、测试输出保持原样(不翻译)。不堆砌:内容太多本身就是阅读负担——先一句话结论,再最少但足够的证据(文档 / 代码 path:line / 真实测试输出,UI 相关必附截图——ui-verify 产出的截图/录屏即此类证据);长日志折叠进 <details>,verdict 只引用结论不重复全量日志。

Usage