菜单
Review a pull request against the shared Review Protocol (correctness, regression, stability, contract, architecture, security). Use when the user asks to "review PR", "check PR", "PR review", or wants an evidence-grounded review of a pull request before merge.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Inspect drift between code, shared workflow references, and Claude, Codex, or Antigravity harness assets after architecture or workflow changes.
This skill should be used when the user asks to "sync guidelines", "document inspection", "check skill updates", "update project-dna", "sync patterns", "verify code-document consistency", or after architecture changes to verify Skills/AGENTS.md/CLAUDE.md match the actual code.
Guide a feature from requirements interview through architecture analysis, security check, and task decomposition.
This skill should be used when the user asks to "plan feature", "design feature", or wants to plan and design a new feature before implementation.
Audit a domain or the full repository for architecture compliance using the shared architecture checklist and repository rules.
Review a pull request or local diff against the repository's shared Review Protocol (correctness, regression, stability, contract, architecture, security, governance).
| name | review-pr |
| argument-hint | PR number, URL, or omit to detect current branch |
| description | Review a pull request against the shared Review Protocol (correctness, regression, stability, contract, architecture, security). Use when the user asks to "review PR", "check PR", "PR review", or wants an evidence-grounded review of a pull request before merge. |
Target: $ARGUMENTS (PR number, GitHub URL, or empty for current branch)
completion gate (final review at end of work)/sync-guidelines if drift detected/review-pr recursively, do not invoke /plan-feature from insideCORR / REG / STAB / CONTRACT / ARCH / SEC / GOV (Phase 1)Drift Candidates and whether Sync Required is true or false (Phase 2)Findings (open) + Coverage (OK/SKIP) +
Verdict (Phase 3)Read docs/ai/shared/skills/review-pr.md for detailed steps, and
docs/ai/shared/review-protocol.md for the shared
dimensions, finding basis, output contract, and posting rules.
For cross-tool review prompts, use the shared procedure's Cross-Tool Review Prompt Template
section; do not duplicate the template here.
Every finding obeys the protocol's Finding Basis rule:
ARCH / SEC / GOV findings must cite a shared rule source (you may navigate via
.claude/rules/architecture-conventions.md, but the citation is the shared checklist / AGENTS.md);
CORR / REG / STAB / CONTRACT findings must cite diff / contract / test / runtime
evidence. A concern with no basis is a Question, not a finding.