القائمة
Use for /wf-review in Claude Code, $wf-review or /skills wf-review in Codex, peer review, second opinion, or cross-model review.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when work needs bounded subagent coordination, parallel read-only exploration, independent review gates, broad context partitioning, or controlled handoffs.
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
Perpetual auto-optimization mode. Never stops until 8-angle exhaustion. Inherits WF acceptance gates and subagent orchestration per cycle. Use for Claude /wf-auto, Codex $wf-auto, auto mode, or unbounded self-directed optimization.
Perpetual inspiration mode for /wf-auto-spark or $wf-auto-spark. Inherits WF-AUTO/WF execution gates while using external spark search, roadmap anchoring, and <=50% deviation guard.
Use for /wf-learn in Claude Code, $wf-learn or /skills wf-learn in Codex, or when the user wants a learning cycle from repeated errors, corrections, patterns, or session history.
Use for /wf-max in Claude Code, $wf-max or /skills wf-max in Codex, or maximum-parallelism Harness work with WF strict-superset gates and CEO -> manager -> worker decomposition.
| name | wf-review |
| description | Use for /wf-review in Claude Code, $wf-review or /skills wf-review in Codex, peer review, second opinion, or cross-model review. |
Use the other available agent CLI for independent review. Never simulate a cross-model review with the same model.
/wf-review [focus] or select the wf-review skill.$wf-review or /skills then choose wf-review.| Runtime | Command |
|---|---|
| Claude Code -> Codex | `git diff |
| Codex -> Claude Code | `git diff |
| Only one CLI | Warn user. Do not self-review. |
Cover correctness, security, architecture, performance, and tests. Classify findings as Critical, High, Medium, or Low. Return raw peer output first, then your severity-classified synthesis.
Include the relevant diff, Harness/architecture.md when architecture is in
scope, and any task acceptance criteria. If the diff is too large, ask for a
narrower scope before invoking the other CLI.