一键导入
requesting-code-review
Use when completing tasks, implementing major features, or before merging -- to dispatch review and verify work meets requirements
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Use when completing tasks, implementing major features, or before merging -- to dispatch review and verify work meets requirements
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when reviewing a spec or task graph for completeness before implementation
Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, logging in, or automating browser actions
Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, logging in, or automating browser actions
Use when decomposing a spec, design, or feature description into a task dependency graph with self-evaluating acceptance criteria
Use when doing creative product, feature, component, functionality, or behavior design work
Use when infrastructure or features are built but before declaring done -- verifies work is wired into the system and actively used
| name | requesting-code-review |
| description | Use when completing tasks, implementing major features, or before merging -- to dispatch review and verify work meets requirements |
Review early, review often. Dispatch a reviewer to catch issues before they cascade.
Mandatory:
Optional but valuable:
BASE_SHA=$(git rev-parse HEAD~1) # or origin/main
HEAD_SHA=$(git rev-parse HEAD)
Provide:
Review changes from {BASE_SHA} to {HEAD_SHA}.
**What was built:** {SUMMARY}
**Requirements:** {PLAN_OR_REQUIREMENTS}
Check for:
- Spec compliance (matches requirements?)
- Code quality (clean, tested, no regressions?)
- Triage as Critical / Important / Minor
Read-Only Review: This review is read-only on this checkout. Do not
mutate the working tree, the index, HEAD, or branch state in any way.
Use `git show`, `git diff`, and `git log` to inspect history. If you
need a working copy of a different revision, check it out into a
separate temporary directory (e.g. `git worktree add /tmp/review-{SHA}
{SHA}`, then `git worktree remove` when done) — never `git checkout
{SHA}` on this checkout, which detaches HEAD, orphans commits, and can
trigger long whole-codebase crawls.
When feedback arrives, invoke receiving-code-review before implementing anything.
| Severity | Action |
|---|---|
| Critical | Fix immediately |
| Important | Fix before proceeding |
| Minor | Note for later |
If reviewer is wrong: push back with technical reasoning.