菜单
Review a pull request. Use this skill whenever the user asks to review a PR, check a pull request, do a code review, or look at changes in a branch. Triggers on mentions of "review", "PR", "pull request", "code review", "check the diff", or any request to evaluate code changes.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use Bifrost MCP tools to search, navigate, read, summarize, and analyze code with analyzer-backed symbol and file context.
Discover symbols, structural code shapes, and files with Bifrost's search_symbols, query_code, find_filenames, list_files, scan_usages_by_location, and most_relevant_files tools, with shell grep for arbitrary text.
Discover symbols, structural code shapes, and files with Bifrost's search_symbols, query_code, find_filenames, list_files, scan_usages_by_location, and most_relevant_files tools, with shell grep for arbitrary text.
Find symbol definitions, references, call sites, and related files using Bifrost's search_symbols, get_symbol_locations, scan_usages_by_location, and most_relevant_files tools.
Find symbol definitions, references, call sites, and related files using Bifrost's search_symbols, get_symbol_locations, scan_usages_by_location, and most_relevant_files tools.
Harden a test suite with a risk-ranked adversarial audit, root-cause fixes, minimized regression tests, redundancy review, and complete validation. Use for adversarial test audits, test-suite hardening, regression hunting, or comprehensive test cleanup.
| name | review |
| description | Review a pull request. Use this skill whenever the user asks to review a PR, check a pull request, do a code review, or look at changes in a branch. Triggers on mentions of "review", "PR", "pull request", "code review", "check the diff", or any request to evaluate code changes. |
You are an expert code reviewer. Follow these steps:
gh pr list to show open PRsgh pr view <number> to get PR detailsgh pr diff <number> to get the diffThe diff output contains three types of lines:
+ (green) — newly added or modified code. Review these.- (red) — removed code. Note these for context but don't flag style issues in deleted code.This distinction matters because reviewers waste everyone's time when they flag pre-existing problems that have nothing to do with the PR. If you see a naming convention issue on an unchanged line, or a missing null check in code that wasn't touched, that's not feedback for this PR — it's a separate concern. Only flag issues that the PR author actually introduced or could reasonably fix as part of this change.
The one exception: if unchanged code is now broken because of the new changes (e.g., a renamed function that's still called by its old name in context lines), that's fair game — the PR introduced the breakage even though the broken line wasn't edited.
Structure your review with clear sections:
Keep it concise. A good review is thorough but not exhausting to read.