菜单
Review a GitHub PR and present findings as author-addressed comments. Use when the user asks to review a PR, gives a PR URL or number, or asks for code review feedback on a pull request. Triggers on phrases like "review this PR", "look at this pull request", "code review", or any GitHub PR link.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Open a GitHub PR for the current branch. Generates a title and description from the diff, and respects the repo's PULL_REQUEST_TEMPLATE if one exists.
Split a large feature branch into multiple smaller PRs of max 20 files each. Use when the user wants to break up a big branch, split changes into stacked or parallel PRs, asks "how do I split this PR", mentions a branch has too many files, or wants a PR splitting strategy. Also triggers on phrases like "split this into PRs", "break up this branch", "chunk these changes", "PR plan", or "too many files in this PR".
Generate a concise PR description based on the changed files and their content. Focus on summarizing the key changes and their impact, rather than providing a detailed line-by-line explanation.
Generate a Slack-friendly triage report of open GitHub PRs for a team, author, or set of repos — pure-prompt variant of pr-review-report with no helper script. Use this skill whenever the user wants a PR review queue summary, a daily/standup PR digest, a reviewer triage list, or asks things like "what PRs does my team owe reviews on", "which of my PRs are waiting on review", "show me the team's open PRs", or "give me a PR status report for org X". The skill buckets each PR into exactly one of Needs attention / Ready to merge / In discussion / Awaiting review so reviewers can focus on what matters most.
Pick up the next task, execute it, verify it, mark it complete, and commit. Use when the user wants to work through tasks one at a time, or says 'do the next task', 'work on the next item', or invokes /work. Optionally accepts a task ID and/or custom instructions.
Generate a Slack-friendly triage report of open GitHub PRs for a team, author, or set of repos. Use this skill whenever the user wants a PR review queue summary, a daily/standup PR digest, a reviewer triage list, or asks things like "what PRs does my team owe reviews on", "which of my PRs are waiting on review", "show me the team's open PRs", or "give me a PR status report for org X". The skill buckets each PR into exactly one of Needs attention / Ready to merge / In discussion / Awaiting review so reviewers can focus on what matters most.
| name | pr-review |
| description | Review a GitHub PR and present findings as author-addressed comments. Use when the user asks to review a PR, gives a PR URL or number, or asks for code review feedback on a pull request. Triggers on phrases like "review this PR", "look at this pull request", "code review", or any GitHub PR link. |
| allowed-tools | Bash, Read, Glob |
Accepts a PR URL (e.g. https://github.com/org/repo/pull/123) or a PR number (for the current repo).
Fetch in parallel:
gh pr view <pr> --json title,body,files,additions,deletions,baseRefName,headRefNamegh pr diff <pr>gh api repos/{owner}/{repo}/pulls/{number}/commentsRead the full diff carefully. For large diffs, read persisted output files fully.
Write a clear explanation of the PR:
Review for: bugs, missing error handling, security issues, performance problems, naming/readability, convention violations, lock file anomalies, unsafe casts/patterns.
Categorize each finding: High, Medium, Low, or Nit.
Print the review directly — do NOT post comments to the PR unless the user explicitly asks.
Format: H2 title with PR name, then a "What this PR does" section explaining the changes (from step 3), followed by issues listed with severity, file:line reference, and concrete suggestion. End with a "Positives" section noting what was done well.