review
Review code with parallel agents — tests, security, Ecto, LiveView, Oban. Use after implementation to catch bugs and anti-patterns before committing.
npx skills add oliver-kriska/claude-elixir-phoenix --skill review --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Review Elixir/Phoenix Code Review code by spawning parallel specialist agents. Find and explain issues — do NOT create tasks or fix anything. ## Usage ``` /phx:review # Auto-detects task ID from branch/commits /phx:review test # Review test files only /phx:review security # Run security audit only /phx:review oban # Review Oban workers only /phx:review deploy # Validate deployment config /phx:review iron-laws # Check Iron Law violations only /phx:review ENA-8931 # Force Linear issue /phx:review #42 # Force GitHub issue /phx:review .claude/plans/auth/plan.md # Force plan / spec file /phx:review --no-requirements # Skip requirements coverage check /phx:review --codex # Add Codex CLI as cross-model reviewer ``` ## Arguments `$ARGUMENTS` = Focus area, task ID, or path to plan/spec file. When no requirements argument is passed, the skill auto-detects a task ID from the branch and recent commits (see `${CLAUDE_SKILL_DIR}/references/requirements-detection.md`). ## Workflow ### Step 1: Identify Changed Files and Prepare Directories **CRITICAL**: Create output dirs BEFORE spawning agents — agents cannot create directories and writes will fail. 1. Determine SLUG via Glob on `.claude/plans/
- Usage
- Arguments
- Workflow
- Step 1: Identify Changed Files and Prepare Directories
- Step 1b: Load Plan Context and Prior Reviews
- Step 1c: Detect Requirements Source (skip on --no-requirements)
- Step 2: Spawn Review Agents (MANDATORY)
- Step 3: Collect and Compress Findings
- Step 3b: Filter Findings (Anti-Noise)
- Step 4: Generate Review Summary
- Step 5: Present Findings and Ask User
- Iron Laws
- Integration
What does the review skill do?
Review code with parallel agents — tests, security, Ecto, LiveView, Oban. Use after implementation to catch bugs and anti-patterns before committing.
How do I install it?
Run `npx skills add oliver-kriska/claude-elixir-phoenix --skill review --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From oliver-kriska/claude-elixir-phoenix, a repository with 515 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.