菜单
Review a diff read-only on three axes, code, behavior versus the plan, and relevancy, into one verdict report. Use before shipping a change. Not for fixing findings or auditing a codebase.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Initialize or refresh the project memory bank. Use when the user wants to set up or regenerate the project's memory files. Not for updating one memory file after it exists or editing a single rule directly.
Guide a project's journey through AIDD, from first setup to shipping a feature. Use when the user says onboard me, where do I start, or what to do next. Not for listing every installed surface.
Design and validate a new SaaS's architecture into an INSTALL.md via Q&A and stack comparison. Use when the user starts a project, chooses a stack, or picks an architecture pattern. Not for editing an existing stack or scaffolding code.
Route a request to generate a context artifact (skill, rule, agent, command, or hook) to its generator when the kind is unnamed. A named kind triggers its generator directly. Not for listing existing artifacts.
Generate a router-based skill across the host AI tools a project uses. Use when the user wants to create, scaffold, or refactor a skill, or turn a workflow into one. Not for other artifacts like rules, agents, commands, hooks.
Generate a coding rule that governs editor and agent behavior across the host AI tools. Use when the user wants to write, add, or refactor a rule, convention, or coding standard. Not for other artifacts like skills, agents, or hooks.
| name | 05-review |
| description | Review a diff read-only on three axes, code, behavior versus the plan, and relevancy, into one verdict report. Use before shipping a change. Not for fixing findings or auditing a codebase. |
| argument-hint | review-code | review-functional | review-relevancy |
| model | opus |
Read-only review of a diff along three axes, code quality, feature behavior, and relevancy, composed into one report.
| # | Action | Axis |
|---|---|---|
| 01 | review-code | Clean-code quality on the changed lines |
| 02 | review-functional | The diff against the plan's phases and their acceptance criteria |
| 03 | review-relevancy | Does the change belong: fit to the need, rule conformance, no rot |
Run all three by default, composing one report. Run a single axis only when the caller names it; if it is unclear whether they want all or one, ask. Before running an action, read its file in actions/, not only the table or assets.
review.md to disk; the file is the deliverable, never an inline-only verdict.aidd_docs/tasks/<yyyy_mm>/<yyyy_mm_dd>_<slug>/, beside plan.md), or one resolved from the change when it has none.review.md from assets/review-template.md. One shared Findings table for every axis: functional writes the Phases boxes and the Verification table, and appends a functional row to Findings for each unmet criterion tagged fix; code and relevancy append rows to Findings under their Kind. Tables and boxes, no prose, no per-axis sections. The Phase column ties a finding to the plan when one is in scope, - otherwise.assets/review-validator.yml. Before returning, verify against it and remove any section not listed.Axes run lists which axes ran, so a skipped code or relevancy axis is visible even though Findings is shared. An axis that did not run marks the sections it owns "Not run" (functional owns Phases and Verification); it never leaves a placeholder or invents data.review.md with the current review. It is a snapshot of the current diff, not a history; a later review of the same work replaces the earlier one.references/review-rubric.md.references/review-rubric.md: the severity scale, the verdict rule, the code categories, and the relevancy lenses.assets/review-template.md: the single report the three axes fill.assets/review-validator.yml: the closed set of report sections.