elixir-phoenix-review

Review Elixir/Phoenix Code

Review code by spawning parallel specialist agents. Find and explain issues — do NOT create tasks or fix anything.

Usage

`elixir-phoenix-review`                          # Review all changed files
`elixir-phoenix-review` test                     # Review test files only
`elixir-phoenix-review` security                 # Run security audit only
`elixir-phoenix-review` oban                     # Review Oban workers only
`elixir-phoenix-review` deploy                   # Validate deployment config
`elixir-phoenix-review` iron-laws                # Check Iron Law violations only
`elixir-phoenix-review` .codex/plans/auth/plan.md    # Review implementation of plan

Arguments

$ARGUMENTS = Focus area or path to plan file.

Workflow

Step 1: Identify Changed Files and Prepare Directories

CRITICAL: Create output dirs BEFORE spawning agents — agents cannot create directories and will fail repeatedly on writes.

Determine SLUG from the most recent plan directory (use rg --files on .codex/plans/*/), default to "review". Run mkdir -p ".codex/plans/${SLUG}/reviews" ".codex/plans/${SLUG}/summaries" and mkdir -p .codex/reviews.

Then run git diff --name-only HEAD~5 and git diff --name-only main to identify changed files. Save the diff base for pre-existing detection in Step 3b.

Step 1b: Load Plan Context (Scratchpad)

If reviewing a plan, read .codex/plans/${SLUG}/scratchpad.md for planning decisions, rationale, and handoff notes. Include relevant decisions in each agent's prompt so they have context about WHY code was written a certain way. This eliminates session archaeology.

Step 1c: Check Prior Reviews

If .codex/plans/${SLUG}/reviews/ has prior output, include consolidated summary in each agent's prompt as "PRIOR FINDINGS" with instruction: "Focus on NEW issues. Mark still-present issues as PERSISTENT."

Step 2: Create Task List and Spawn Review Agents (MANDATORY)

NEVER spawn the same agent role twice in one review. If reviewing a plan, scope ALL agents to the plan's changed files in a single pass. Do NOT run a scoped review followed by a broader review — one pass per role.