菜单
Review a diff, branch, PR, or work-in-progress change against the requested spec, repo standards, architecture, and likely regressions. Use before committing non-trivial work.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Ask which skill or flow fits your situation. A router over the skills in this repo.
Implement a piece of work based on a spec or set of tickets.
Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.
Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker — edges as text in one file per ticket locally, or native blocking links on a real tracker.
Plan a huge chunk of work — more than one agent session can hold — as a shared map of investigation tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
| name | review |
| description | Review a diff, branch, PR, or work-in-progress change against the requested spec, repo standards, architecture, and likely regressions. Use before committing non-trivial work. |
Uses scratch working memory.
Purpose: answer whether the diff matches the spec, standards, architecture, and project intent.
NEVER run git add, git commit, git push, git stash, or any mutating git command.
NEVER write, modify, or delete any application source file.
This skill is read-only. If you find issues, report them as findings. Do NOT fix them.
Violation of this rule is a critical failure.
Review only. Do not patch application source. As system-architect, edits are limited to Markdown, .scratch/, and docs/.
Use the narrowest target that fits the request:
main, master, or merge-base) when asked to review a branch.If the target is unclear, ask one short question and stop.
Start with:
git status --shortgit diff --statgit diff --cached --stat when staged changes existThen read targeted diffs only:
git diff -- <file>git diff --cached -- <file>git diff <base>...HEAD -- <file>Read relevant specs, issues, PRDs, standards, docs, ADRs, security notes, or project conventions only when they affect the changed area or the user requested that axis.
Initialize session: .scratch/reviews/<YYYY-MM-DD>/zoo-code-review-<slug>/
Write <session-dir>/session.md with review target, base ref, scope.
Analyze and write <session-dir>/standards.md:
Read <session-dir>/standards.md for context.
Analyze and write <session-dir>/spec.md:
Cross-reference standards findings where relevant.
Read <session-dir>/standards.md and <session-dir>/spec.md.
Analyze and write <session-dir>/security.md:
For every Security/Risk finding, include severity and mitigation. Cross-reference previous passes.
Omit this axis when the change clearly cannot affect security (copy changes, comment fixes, test-only additions, docs-only updates).
Order findings by severity:
For every finding include:
Prefer concrete findings over commentary. If no findings exist for a severity, omit that severity.
End with exactly one result line:
Review result: approveReview result: approve with nitsReview result: changes requestedReview result: blockedRead all angle files from <session-dir>/ (standards.md, spec.md, security.md if present).
Write <session-dir>/synthesis.md with:
approve / approve with nits / changes requested / blockedCall attempt_completion with:
<session-dir>/synthesis.md path
brief result line (approve / approve with nits / changes requested / blocked)
recommended next command
small fix -> /zoo-tweak
behavior fix -> /zoo-tdd
unknown cause -> /zoo-fix
design issue -> /zoo-refactor
ready for evidence -> /zoo-verify
Do not auto-launch any follow-up command.