菜单
Use when a pull request needs a serious pre-merge review covering correctness, edge cases, security, tests, documentation, and architecture.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | review-pr |
| version | 1.0.0 |
| description | Use when a pull request needs a serious pre-merge review covering correctness, edge cases, security, tests, documentation, and architecture. |
| activation | {"patterns":["review.*pr","code review"],"keywords":["review","pr","pull request"],"max_context_tokens":2500} |
Use this skill when the user wants a serious pre-merge review.
gh auth status succeeds if GitHub data must be fetchedAGENTS.md is available for project-specific rulesAGENTS.md.Do not review from the diff alone.
For each changed file:
Always check whether the change follows the rules in AGENTS.md.
Present findings sorted by severity with:
Also give:
If the user wants GitHub comments, post the result after presenting it.
Use this structure:
| # | Severity | File:Line | Finding | Suggestion |
|---|
Then include:
Use when a GitHub issue should be handled end-to-end, including issue analysis, code changes, tests, verification, and an optional commit.
Use when working with GitHub repositories, issues, pull requests, branches, or commits and the task needs authenticated repository operations or GitHub metadata.
Use when a task needs a written execution plan with explicit steps, risks, verification, and user approval before implementation starts.
Use when a pull request needs one coordinated workflow covering review state, fixes, checks, branch updates, and merge readiness.
Use when a pull request already has review feedback that needs triage, code changes, verification, and clear replies back to reviewers.
Use when deciding whether a change is ready to merge and a concise cross-language checklist is more useful than a full narrative review.