in parallel, then cross-validate and synthesize into one unified report — like a review board where two reviewers examine the code independently, and Claude as lead reviewer delivers the final opinion.
Prerequisites
Codex CLI
Install with
npm i -g @openai/codex
, authenticate with
codex login
If only one CLI is installed, fall back to the available reviewer with a warning — the review still has value with fewer perspectives, so don't fail entirely.
When to Use
Reviewing uncommitted changes before committing
Auditing a branch diff before opening a PR
Reviewing a specific commit for regressions
When NOT to Use
Reviewing documentation, markdown, or non-code files
Trivial single-line changes where a full council review would be overkill
Workflow
DO NOT read script source code.
Run scripts directly and use
--help
for usage.
Step 1: Determine Review Scope
If the scope is not already clear, use AskUserQuestion to ask:
Uncommitted changes
(default) — staged, unstaged, and untracked changes
Branch diff
— compare current branch against a base branch
Specific commit
— audit a single changeset
Step 2: Run Both Reviews in Parallel
Both reviewers read the same diff independently — neither depends on the other's output. Launch them both at once in a single message to eliminate sequential wait time.
Scripts are in
scripts/
relative to this skill's directory and enforce the correct model and read-only mode internally. Run