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 從公開儲存庫中收錄這些內容。

檢舉或申請下架