review
Request a read-only adversarial review from Claude Code through the sandbox-external bridge.
Install
npx skills add https://github.com/Borda/AI-Rig/tree/main/plugins/bridge_cc-codex/codex-skills/review
claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install borda-ai-rig@llmmart
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
Before asking, read User Questions.
Ask Claude Code to Review
Call bridge_review with required task; preserve caller-supplied model, effort, timeout_seconds, depth, and run_id. If effort absent, select and pass it: low for narrow mechanical or settled factual work; medium for bounded implementation, diagnosis, or review; high for cross-file, adversarial, architectural, or security judgment; xhigh for unusually broad consequential work; max only on explicit request. Never replace supplied effort.
MCP host binds its launch workspace. Return only compact envelope; retain workspace-relative transcript and incident references for detail, never inline peer details.
If status=blocked, open the JSON file referenced by incident; inspect its fault. For output-limit, report no review verdict. Split by file, module, or symbol; use fresh read-only calls with bounded tool output. Reconcile every scope; disclose unanswered work. Never treat transcript fragments as a completed review.
Files (ai-rig)
-
SKILL.md 1.2 KB
--- name: review description: Request a read-only adversarial review from Claude Code through the sandbox-external bridge. --- > Before asking, read [User Questions](../../rules/codex-user-questions.md). # Ask Claude Code to Review Call `bridge_review` with required `task`; preserve caller-supplied `model`, `effort`, `timeout_seconds`, `depth`, and `run_id`. If effort absent, select and pass it: `low` for narrow mechanical or settled factual work; `medium` for bounded implementation, diagnosis, or review; `high` for cross-file, adversarial, architectural, or security judgment; `xhigh` for unusually broad consequential work; `max` only on explicit request. Never replace supplied effort. MCP host binds its launch workspace. Return only compact envelope; retain workspace-relative transcript and `incident` references for detail, never inline peer `details`. If `status=blocked`, open the JSON file referenced by `incident`; inspect its `fault`. For `output-limit`, report no review verdict. Split by file, module, or symbol; use fresh read-only calls with bounded tool output. Reconcile every scope; disclose unanswered work. Never treat transcript fragments as a completed review.
Comments (0)
Sign in to join the conversation.
Reviews (0)
No reviews yet.
No comments yet.