phxreview

Solid

Review code with parallel agents — tests, security, Ecto, LiveView, Oban. Use after implementation to catch bugs and anti-patterns before committing.

Code & Development 384 stars 25 forks Updated 4 days ago MIT

Install

View on GitHub

Quality Score: 92/100

Stars 20%
86
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# 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 ``` ## 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 current git branch name 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/*/` (default: `"review"`) 2. Run `mkdir -p ".claude/plans/${SLUG}/reviews" ".claude/plans/${SLUG}/summaries" .claude/reviews` 3. Run `git diff --name-only HEAD~5` and `git ...

Details

Author
oliver-kriska
Repository
oliver-kriska/claude-elixir-phoenix
Created
3 months ago
Last Updated
4 days ago
Language
Python
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category