‹ 首页

review-pr

@fcakyon · 收录于 1 周前 · 上游提交 6 天前

This skill should be used when user asks to "review a PR", "review pull request", "review this pr", "code review this PR", "check PR

场景代码评审合并前检查

适合你，如果经常需要审查团队成员的代码变更

/ 下载安装
review-pr.skill双击,或拖进 Claude 桌面版 / Cowork,即完成安装↓ .skill↓ .zip
用别的 agent?下载 .zip 解压,把文件夹放进它的技能目录
Claude Code~/.claude/skills/(项目级 .claude/skills/)
Codex CLI~/.codex/skills/
Cursor自动读取上面两处目录
其他工具见其文档的「skills」目录;两个下载是同一份文件,只是名字不同
/ 通过 npx 安装 校验哈希
npx oh-my-skill add fcakyon/claude-codex-settings/review-pr
/ 通过 bash 安装
curl -fsSL https://oh-my-skill.com/install.sh | bash -s -- fcakyon/claude-codex-settings/review-pr
/ 已经装过?验证本机副本,不用重装
npx oh-my-skill verify fcakyon/claude-codex-settings/review-pr
安装目标可用 --agent / --scope 或 --to 明确指定;省略时只会在唯一已存在的 agent 目录上自动选择,零命中或多命中会停止并提示。content_hash 缺失或不一致均拒装。
773GitHub stars
~460上下文体积 · 单文件
镜像托管

怎么用

技能原文 SKILL.md作者撰写 · Apache-2.0 · 44b7c00

Review PR

Review a pull request for bugs, regressions, missing tests, and risky changes.

When explicitly invoked with extra text, treat that text as the PR number or URL. If no PR reference is provided, infer it from the current branch.

Process
  1. Preferred execution
  2. If subagents are available, use github-dev:pr-reviewer and pass the PR reference.
  3. Otherwise follow the manual steps below.
  1. Parse PR reference
  2. If a PR number or URL is provided, extract owner, repo, and PR number.
  3. If not, auto-detect the PR from the current branch with gh pr view --json number,headRefName.
  1. Fetch PR data
  2. Use gh pr diff <number> for the full diff.
  3. Use gh pr view <number> --json files for the changed file list.
  4. Skip generated or vendored files such as .lock, .min.js, .min.css, dist/, build/, vendor/, node_modules/, _pb2.py, and images.
  1. Review focus
  2. Only report issues that require fixes.
  3. Only review PR changes, never pre-existing issues in unchanged code.
  4. Prioritize bugs, security issues, breaking changes, performance issues, edge cases, and missing tests.
  5. Combine related issues that share the same root cause.
  6. Keep the list short and high signal.
  1. Review comment rules
  2. Only create pending PR comments, never submit or confirm the review automatically.
  3. Use gh for GitHub operations.
  4. Start comments in lowercase, keep them short, avoid end punctuation when possible.
  5. Use simple language for both bot-facing and human-facing comments.
Output Format

If issues are found, report them in descending severity with file references and a final recommendation of NEEDS_CHANGES.

If no issues are found, return APPROVE - No fixes required.

按 Apache-2.0 许可原样转载,未经改动 · 在 GitHub 查看 →

评论

登录即可评论;带「已验证安装」的,是发布者名下有本店的安装或持有记录。
…