Menu
Use when writing code, fixing a bug, implementing a feature, or improving code structure. Invoked for typed implementation work inside `crates/`, `test/`, `website/`, or other source surfaces.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when a diff or PR is too big to review by eye and the question is "what should I actually look at" โ sorts each changed line into wire / CLI / API / logic / test / doc tiers, then opens a clickable local page with the real hunks. A reading order, never a verdict.
Use to implement a plan artifact from `/swarm-plan`, or a free-text implementation task with contract-first TDD + Review-Fix Loop. Tier (`low | auto | high | max`) scales builder model, loop rounds, review breadth, and Codex code-diff gate.
Use for branch, PR, or diff review before landing on main. Tier (`low | auto | high | max`) scales breadth from single reviewer to adversarial panel with architect + SOTA-gap + Codex cross-model gate. Triggers: "review", "/swarm-review", pre-merge checks.
Use when the user says "commit", "/commit", "save progress", or asks to land working changes on a feature or worktree branch. OCX working-phase posture โ minimises commit count, can amend rolling Checkpoints, offers a one-time PR prompt. For pre-merge cleanup, use `/finalize`.
Use for feature planning, task decomposition, multi-perspective research, or ADR scaffolding. Tier (`low | auto | high | max`) scales research depth, architect model, and review breadth. Canonical research primitive for AI config / ADR work.
Use when the user says "codex review", "/codex-adversary", "adversarial review", "cross-model review", or asks for a different-model second opinion on a diff or plan artifact. Complements `/swarm-review` via Codex-CLI. Scopes: code-diff (default), plan-artifact (gate for `/swarm-plan`).
| name | builder |
| description | Use when writing code, fixing a bug, implementing a feature, or improving code structure. Invoked for typed implementation work inside `crates/`, `test/`, `website/`, or other source surfaces. |
| user-invocable | true |
| argument-hint | task-description |
| triggers | ["fix the bug","fix this bug","refactor this","refactor the","write the code"] |
Role: turn plans into working, tested, production-ready OCX code.
Follow contract-first TDD phases in .claude/rules/workflow-feature.md:
unimplemented!(). Gate: cargo check.task verify before mark complete.quality-core.md).claude/rules/quality-core.md + quality-rust.md โ universal + Rust quality gates.claude/rules/workflow-feature.md โ TDD phases.claude/rules/subsystem-cli.md โ command pattern, Printable, Api layer.claude/rules/subsystem-package-manager.md โ task methods, three-layer errors.claude/rules/subsystem-file-structure.md โ stores, ReferenceManager (arg order gotcha).claude/rules/subsystem-package.md, subsystem-oci.md โ when touch metadata or registry.claude/rules/arch-principles.md โ pattern catalog (auto-load on Rust files)mcp__context7__resolve-library-id + mcp__context7__get-library-docs) โ query current crate APIs (tokio, oci-client, clap, serde, โฆ) before guess. Training-data API knowledge decay fast.task runner โ never run ad-hoc cargo/pytest when task command exists. task --list to discover.cargo fmt before commit; task verify before mark complete$ARGUMENTS