菜单
Use when worker has completed implementation and code needs systematic review before proceeding. Works for both same-model and cross-model review.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when the user submits a new feature request or complex change that needs structured clarification before design. Not for simple bug fixes, config changes, or minor edits that can go directly to implementation.
Use after requirement clarification is complete, to produce a technical design document before any code is written. Not for simple tasks that don't need architecture planning.
Use when technical design is complete and approved, to produce a bite-sized implementation plan with exact file paths, code, and commands.
Use after docs-reviewer has completed compliance review, to perform adversarial/critical review of design or plan documents. Focuses on questioning decisions, finding blind spots, and checking edge cases that compliance review misses.
Use when a design document or implementation plan has been produced and needs compliance review before adversarial review. Checks coverage, consistency, feasibility against upstream documents.
| name | review-code |
| description | Use when worker has completed implementation and code needs systematic review before proceeding. Works for both same-model and cross-model review. |
对 worker 提交的代码变更进行系统审查。不修改代码，只出审查报告。
docs/feature/当次日期/03-plan.md，确认本次任务的范围。AGENTS.md，理解代码风格、命名约定、包结构。git status --short 查看范围，git diff 查看未暂存变更，git diff --staged 查看已暂存变更。仅当 Master 明确说明代码已提交时，才使用 git diff HEAD~1。./review-template.md 格式的报告给 Master。| 维度 | 检查什么 |
|---|---|
| 正确性 | 实现与计划一致吗？逻辑有漏洞吗？边界条件处理了吗？ |
| 设计 | 符合 02-design.md 的架构吗？新代码与现有模块的边界清晰吗？ |
| 风格 | 符合 AGENTS.md 和项目现有代码风格吗？命名、包结构、异常处理方式一致吗？ |
| 测试 | 测试覆盖了关键路径和边界吗？测试真实可运行还是 mock 一切？ |
| 安全 | 输入校验、权限检查、SQL 注入、敏感信息泄露 |
| 性能 | N+1 查询、不必要的数据库调用、大循环内的重复操作 |
按 ./review-template.md 格式出报告。报告开头必须有 Verdict 裁决字段（PASS / PASS_WITH_NOTES / BLOCKED）及各等级问题计数。
git status / git diff 类命令用于审查变更范围