Back to Details

review

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Review (Reviewer-Only Pass)

审核（仅审核者可执行流程）

Review is a shorthand alias for 
/plan --review
. It triggers Critic evaluation of an existing plan and is intended to preserve writer/reviewer separation.
Review是
/plan --review
的简写别名。它会触发Critic对现有计划进行评估，旨在保证编写者/审核者的权责分离。

Usage

使用方法

/review
/review "path/to/plan.md"
/review
/review "path/to/plan.md"

Behavior

行为

This skill invokes the Plan skill in review mode:
/plan --review <arguments>
The review workflow:
  1. Treat review as a reviewer-only pass. The authoring context may write the plan or cleanup proposal, but a separate reviewer context must issue the verdict.
  2. Read plan file from 
    .omx/plans/
    (or specified path)
  3. Evaluate via Critic agent
  4. For cleanup/refactor/anti-slop work, confirm the artifact includes a cleanup plan, regression-test coverage or an explicit test gap, bounded smell-by-smell passes, and quality gates.
  5. Return verdict: APPROVED, REVISE (with specific feedback), or REJECT (replanning required)
该skill会以审核模式调用Plan skill：
/plan --review <arguments>
审核工作流：
  1. 将审核视为仅审核者可执行的流程。编写上下文可以撰写计划或清理提案，但必须由独立的审核上下文给出最终结论。
  2. 从
    .omx/plans/
    （或指定路径）读取计划文件
  3. 通过Critic Agent进行评估
  4. 对于清理/重构/反冗余工作，需确认制品包含清理计划、回归测试覆盖范围或明确的测试缺口、逐代码异味排查步骤，以及质量门禁。
  5. 返回结论：APPROVED（批准）、REVISE（需修改，附带具体反馈）或REJECT（拒绝，需要重新制定计划）

Guardrails

防护规则

  • Never write and approve in the same context.
  • If the current context authored the artifact, hand review to Critic or another reviewer role.
  • Approval must cite concrete evidence, not author claims.
Follow the Plan skill's full documentation for review mode details.
  • 禁止在同一上下文内同时执行编写和批准操作。
  • 如果当前上下文是制品的编写方，需将审核工作移交给Critic或其他审核角色。
  • 批准必须引用具体证据，不能仅依据编写者的声明。
如需了解审核模式的详细信息，请查阅Plan skill的完整文档。