Claude Skill

review

Request a read-only adversarial Codex review with explicit model, effort, budget, and compact findings.

LLM Mart · 0 points · 16 0 0

Virus-scanned Reviewed automatically before listing.

Full trust report

Download Borda-AI-Rig-plugins_bridge_cc-codex_claude-skills_review-39e3a48.zip · 1 KB

borda/ai-rig 27 4 forks Apache-2.0 Updated 2d ago

Part of borda/ai-rig — 82 skills

Install

skills CLI npx skills add https://github.com/Borda/AI-Rig/tree/main/plugins/bridge_cc-codex/claude-skills/review

Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install borda-ai-rig@llmmart

Git git clone https://github.com/Borda/AI-Rig.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole borda/ai-rig collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Ask Codex to Review

Parse $ARGUMENTS: required review instructions; optional model, effort, timeout-seconds, depth, run-id, workspace. Reject empty review instructions. Not a general question; for that use /bridge:advise. Effort omitted: classify complete scope, pass level explicitly. Preserve caller-supplied level. Tiers: minimal = trivial lookup or one-line mechanical confirmation; low = narrow mechanical change or settled fact; medium = bounded implementation, diagnosis, or review; high = cross-file, adversarial, architectural, or security judgment; xhigh = unusually broad and consequential; max = explicit caller request only.

Run python "${CLAUDE_PLUGIN_ROOT}/bin/bridge_call.py" review --task "<instructions>"; pass each option separately. For quoted text you did not author, use scratch file + --task-file <path> instead of --task; mutually exclusive. Bridge runs read-only ephemeral Codex execution with adversarial-review prompt; default soft budget 300 seconds. Never resume review.

Return compact JSON envelope. Keep bounded transcript at bridge-reported workspace-relative artifact path. Never inline peer details.

If status=blocked, open the JSON file referenced by incident and inspect its fault; incident may be null — then report blocked with no incident detail. For output-limit, report no review verdict. Split by file, module, or symbol; use fresh read-only calls with bounded tool output. If status=timeout, report the returned effort and the unreviewed scope; narrow the scope or raise --timeout-seconds — never resend at a higher effort against the same budget. If status=refused, report its fault: a request at inherited depth one or greater is refused (recursion-depth); never retry — the request already exceeded permitted cross-host chain depth. Reconcile every scope; disclose unanswered work. Never treat transcript fragments as a completed review.

Files (ai-rig)

SKILL.md 2.2 KB

---
name: review
description: Request a read-only adversarial Codex review with explicit model, effort, budget, and compact findings.
argument-hint: '[--model MODEL] [--effort LEVEL] [--timeout-seconds N] REVIEW_INSTRUCTIONS'
allowed-tools: Bash
---

# Ask Codex to Review

Parse `$ARGUMENTS`: required review instructions; optional `model`, `effort`, `timeout-seconds`, `depth`, `run-id`, `workspace`. Reject empty review instructions. Not a general question; for that use `/bridge:advise`. Effort omitted: classify complete scope, pass level explicitly. Preserve caller-supplied level. Tiers: `minimal` = trivial lookup or one-line mechanical confirmation; `low` = narrow mechanical change or settled fact; `medium` = bounded implementation, diagnosis, or review; `high` = cross-file, adversarial, architectural, or security judgment; `xhigh` = unusually broad and consequential; `max` = explicit caller request only.

Run `python "${CLAUDE_PLUGIN_ROOT}/bin/bridge_call.py" review --task "<instructions>"`; pass each option separately. For quoted text you did not author, use scratch file + `--task-file <path>` instead of `--task`; mutually exclusive. Bridge runs read-only ephemeral Codex execution with adversarial-review prompt; default soft budget 300 seconds. Never resume review.

Return compact JSON envelope. Keep bounded transcript at bridge-reported workspace-relative artifact path. Never inline peer `details`.

If `status=blocked`, open the JSON file referenced by `incident` and inspect its `fault`; `incident` may be `null` — then report blocked with no incident detail. For `output-limit`, report no review verdict. Split by file, module, or symbol; use fresh read-only calls with bounded tool output. If `status=timeout`, report the returned `effort` and the unreviewed scope; narrow the scope or raise `--timeout-seconds` — never resend at a higher effort against the same budget. If `status=refused`, report its `fault`: a request at inherited depth one or greater is refused (`recursion-depth`); never retry — the request already exceeded permitted cross-host chain depth. Reconcile every scope; disclose unanswered work. Never treat transcript fragments as a completed review.