Adversarial Review

poteto/noodle/.agents/skills/adversarial-review

作者 poteto82d2921c52370f23f29086de81ccfb600939c037无许可证收录于 2026年10月9日更新于 2026年10月9日

Adversarial code review using cross-model approach. Spawns reviewers on the opposing model (Claude uses Codex, Codex uses Claude) to challenge work from distinct critical lenses. Produces a synthesized verdict with findings and lead judgment. Triggers: "adversarial review".

AI 生成的概览

通过在对立 AI 模型上启动评审者并综合裁决,执行对抗式代码评审。

功能
该技能编排对抗式代码评审:先加载治理原则,确定变更的范围与意图,并评估变更规模以决定启动多少名评审者。评审者在对立模型的 CLI 上运行(主导方为 Claude 时用 Codex,主导方为 Codex 时用 Claude),并从不同视角(如怀疑者、架构师、极简主义者)对工作提出质疑。其输出会被核验、去重并综合为一份裁决,随后由主导方追加自身判断,说明接受或拒绝哪些发现。它只产出裁决文档,不做任何修改。
适用场景
适用于产生大型差异(200 行以上)的会话之后、实施计划阶段之后,或完成规划会话之后,在验收前需要从独立批判视角挑战工作时。
运行要求
需要可运行的对立模型 CLI(codex exec 或 claude -p)、包含链接原则文件的 brain/principles.md,以及随附的视角、评审者提示词和裁决格式参考文件。该技能不附带脚本,仅为指令,评审者默认只读。

Adversarial Review

Spawn reviewers on the opposite model to challenge work. Reviewers attack from distinct lenses grounded in brain principles. The deliverable is a synthesized verdict — do NOT make changes.

Hard constraint: Reviewers MUST run via the opposite model's CLI (codex exec or claude -p). Do NOT use subagents, the Agent tool, or any internal delegation mechanism as reviewers — those run on your own model, which defeats the purpose.

Step 1 — Load Principles

Read brain/principles.md. Follow every [[wikilink]] and read each linked principle file. These govern reviewer judgments.

Step 2 — Determine Scope and Intent

Identify what to review from context (recent diffs, referenced plans, user message).

Determine the intent — what the author is trying to achieve. This is critical: reviewers challenge whether the work achieves the intent well, not whether the intent is correct. State the intent explicitly before proceeding.

Assess change size:

SizeThresholdReviewers
Small< 50 lines, 1-2 files1 (Skeptic)
Medium50-200 lines, 3-5 files2 (Skeptic + Architect)
Large200+ lines or 5+ files3 (Skeptic + Architect + Minimalist)

Read references/reviewer-lenses.md for lens definitions.

Step 3 — Detect Model and Spawn Reviewers

Create a temp directory for reviewer output:

sh
REVIEW_DIR=$(mktemp -d /tmp/adversarial-review.XXXXXX)

Determine which model you are, then spawn reviewers on the opposite:

If you are Claude — spawn Codex reviewers via codex exec:

sh
codex exec --skip-git-repo-check -o "$REVIEW_DIR/skeptic.md" "prompt" 2>/dev/null

Use --profile edit only if the reviewer needs to run tests. Default to read-only. Run with run_in_background: true, monitor via TaskOutput with block: true, timeout: 600000.

If you are Codex — spawn Claude reviewers via claude CLI:

sh
claude -p "prompt" > "$REVIEW_DIR/skeptic.md" 2>/dev/null

Run with run_in_background: true.

Name each output file after the lens: skeptic.md, architect.md, minimalist.md.

Build each reviewer's prompt using the template in references/reviewer-prompt.md.

Step 4 — Verify and Synthesize Verdict

Before reading reviewer output, log which CLI was used and confirm the output files exist:

sh
echo "reviewer_cli=codex|claude"ls "$REVIEW_DIR"/*.md

If any output file is missing or empty, note the failure in the verdict — do not silently skip a reviewer.

Read each reviewer's output file from $REVIEW_DIR/. Deduplicate overlapping findings. Produce a single verdict using the format in references/verdict-format.md.

Step 5 — Render Judgment

After synthesizing the reviewers, apply your own judgment. Using the stated intent and brain principles as your frame, state which findings you would accept and which you would reject — and why. Reviewers are adversarial by design; not every finding warrants action. Call out false positives, overreach, and findings that mistake style for substance.

Append the Lead Judgment section to the verdict (see references/verdict-format.md).

来源与署名

来源:poteto/noodle位于.agents/skills/adversarial-review提交82d2921

许可证: 无许可证

内容归原作者所有。SourceWeft 从公开仓库中收录这些内容。

举报或申请下架