Review

Skill RadOrigin-LLC/RAD-Claude-Skills/plugins/rad-codex/skills/review

Marketplace of plugins and skills for Claude Code

Install

npx -y skills add RadOrigin-LLC/RAD-Claude-Skills --skill review

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Cross-model code review — have the local OpenAI Codex CLI (GPT-5.5) review the working diff, a branch delta, or a specific commit and return findings for Claude to verify. Use when the user says "codex review", "have codex review this", "get a second set of eyes / second opinion on this diff", "cross-model review", or before shipping high-stakes changes when an independent GPT perspective is wanted alongside Claude's own review.

SKILL.md

2.7 KB, 562 tokens by cl100k_base, as published. Nobody here has run it

Cross-model review via Codex

GPT-5.5 catches different bug classes than Claude — that blind-spot coverage is the whole value. Run it through Codex's built-in review mode, which knows how to walk a diff; don't hand-roll a review prompt over exec.

Invocation

Via the Bash tool. -C must point inside the git repo (review mode requires one). Codex accepts either a scope flag or custom instructions — never both (the CLI rejects the combination; the runner errors early on it).

Standard case — scope flag, built-in review contract (usually what you want; Codex's own review prompt is well-tuned):

bash "${CLAUDE_PLUGIN_ROOT}/scripts/codex-run.sh" --review -C "/r/Dev/apps/Faunero" -e high -- --uncommitted </dev/null

Scope selectors (exactly one, after --):

--uncommitted — staged + unstaged + untracked (review Claude's own working diff before commit)
--base main — everything this branch adds over main
--commit <sha> — one commit

Focused case — custom instructions, no scope flag (name the scope inside the prompt instead):

bash "${CLAUDE_PLUGIN_ROOT}/scripts/codex-run.sh" --review -C "/r/Dev/apps/Faunero" -e high <<'EOF'
Review the uncommitted changes for correctness bugs and security issues only —
skip style. For every finding: file:line, severity (P0-P3), the concrete
failure scenario, and the minimal fix. Say "no findings" if clean.
EOF

Review runs are read-only by nature. Use -e high — review is exactly the workload where reasoning effort pays. Expect a few minutes; set the Bash timeout to 600000, or use run_in_background: true for big diffs.

Handling findings — one round, filtered

Verify each finding yourself against the actual code before acting. Cross-model review has real false positives, and the two models trade stylistic preferences if you let them.
Fix what's confirmed; explicitly note what you rejected and why in your report to the user.
Cap at one round-trip. Do not send the fixes back to Codex for re-review unless the user asks — iterated cross-review degenerates into style ping-pong and burns quota.