Stats
Actions
Tags
From judge-codex
Internal helper contract for calling the codex-companion-judge runtime. Used by `judge-codex-jury` only.
How this skill is triggered — by the user, by Claude, or both
Slash command
/judge-codex:codex-cli-runtimeThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
```bash
node "${CLAUDE_PLUGIN_ROOT}/scripts/codex-companion-judge.mjs" <subcommand> [args]
| Subcommand | Purpose |
|---|---|
judge --stage <stage> --slug <slug> | Single-stage judge run |
auto --slug <slug> | End-to-end 4-stage run |
status | List background jobs + recent outputs |
setup | Verify codex CLI availability + login |
codex CLI on PATH (@openai/codex npm package, install via /judge-codex:setup or npm install -g @openai/codex).codex auth status returns OK).codex exec --json --model "${MODEL:-gpt-5-codex}" --effort "${EFFORT:-medium}" \
"<prompt assembled from artifact + golden-rule + judge agent system prompt>"
The companion script:
rules/ or .claude/rules/.${CLAUDE_PLUGIN_ROOT}/agents/<stage>-judge.md.codex exec --json and pipes the output through a JSON-schema validator.knowledge-base/judge-codex/<slug>-<stage>-judge-<date>.json.judge-codex-jury subagent to forward verbatim.judge-codex-jury subagent makes EXACTLY ONE Bash call to this script per request.codex CLI is absent, the script exits 1 with a clear message — the subagent returns nothing.--background is handled by Claude Code's Bash(..., run_in_background: true), not by the script.| Flag | Meaning |
|---|---|
--model <name> | Override Codex model (default: gpt-5-codex) |
--effort <level> | Reasoning effort (default: medium) |
--wait / --background | Execution mode (handled by Claude Code) |
--stop-on-disagreement | (auto only) Halt at first stage that disagrees with the Claude-side verdict |
--no-quality-evaluator | (auto only) Skip the keep/discard gate — NOT recommended; for debugging only |
knowledge-base/judge-codex/.npx claudepluginhub usetheodev/judge-codex-plugin-cc --plugin judge-codexProvides a checklist for code reviews covering functionality, security, performance, maintainability, tests, and quality. Use for pull requests, audits, team standards, and developer training.