Agent Skills
› fcakyon/claude-codex-settings
› review-pr
review-pr
GitHub用于审查代码拉取请求，识别缺陷、回归、缺失测试及风险变更。支持自动解析PR引用，优先使用子代理或手动执行，仅报告需修复的问题并生成评论，不自动提交审核。
Trigger Scenarios
review a PR
review pull request
review this pr
code review this PR
Install
npx skills add fcakyon/claude-codex-settings --skill review-pr -g -y
SKILL.md
Frontmatter
{
"name": "review-pr",
"description": "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
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
-
Preferred execution
- If subagents are available, use
github-dev:pr-reviewerand pass the PR reference. - Otherwise follow the manual steps below.
- If subagents are available, use
-
Parse PR reference
- If a PR number or URL is provided, extract owner, repo, and PR number.
- If not, auto-detect the PR from the current branch with
gh pr view --json number,headRefName.
-
Fetch PR data
- Use
gh pr diff <number>for the full diff. - Use
gh pr view <number> --json filesfor the changed file list. - Skip generated or vendored files such as
.lock,.min.js,.min.css,dist/,build/,vendor/,node_modules/,_pb2.py, and images.
- Use
-
Review focus
- Only report issues that require fixes.
- Only review PR changes, never pre-existing issues in unchanged code.
- Prioritize bugs, security issues, breaking changes, performance issues, edge cases, and missing tests.
- Combine related issues that share the same root cause.
- Keep the list short and high signal.
-
Review comment rules
- Only create pending PR comments, never submit or confirm the review automatically.
- Use
ghfor GitHub operations. - Start comments in lowercase, keep them short, avoid end punctuation when possible.
- 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.
Version History
- 9d0ce8b Current 2026-07-25 10:34
