Deep code review - Elixir idioms, Phoenix patterns, architecture, safety. Launches 3 parallel reviewers + plan-reviewer gate. Use when: review, review this, code review, check this code, review my changes, is this good, what do you think, code smells.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Reviews current changes for correctness, idioms, architecture, and Phoenix/LiveView patterns. Three parallel code-reviewer agents with focused scopes, aggregated findings, and a plan-reviewer critique before presenting fixes.
Get the full diff and diff stat against main:
git diff main...HEAD
git diff main...HEAD --stat
Launch 3 code-reviewer agents in parallel (single message, 3 Agent tool calls). Each gets the full diff but a focused mandate.
CRITICAL: Launch all 3 agents in the same message so they run concurrently.
Focus: logic bugs, Ecto changeset errors, LiveView callback correctness, edge cases (nil, empty, missing records), query correctness, transaction safety.
Focus: Elixir idioms (multi-clause over if/else, no unless, no nested case), Phoenix patterns (contexts as boundary, thin LiveView, streams), DDD boundaries (Blog/Import/Export), module size <200 lines.
Focus: test coverage for new public functions, CLAUDE.md sync with actual structure, comment quality (WHY not WHAT), proper validations in changesets.
After all 3 agents return, merge findings:
[safety], [idioms], [completeness]If Critical or Important findings exist:
plan-reviewer agent to critique the fix planIf only Minor findings: skip plan-reviewer, present review directly.
Show the aggregated review to the user with verdict and fix plan if needed.
After user approves the plan:
mix test
mix format --check-formatted
mix compile --warnings-as-errors
/dev <issue> -> /review -> /commit -> /pr
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Create a git commit following project conventions. Use when: commit, commit this, make a commit, commit changes, git commit, save changes, commit my work, stage and commit, detailed commit.
The English summary is being prepared. Showing the original description.
Implementer - fetches a GitHub issue, builds an implementation plan, then implements using TDD. Use when: implement, build this, code this, add this feature, TDD, test first, red green refactor, pick a task, next task, dev.
The English summary is being prepared. Showing the original description.
Product Owner - scans codebase and creates or amends GitHub issues with PRD. Use when: PRD, feature, issue, create issue, amend issue, what should we build, plan feature, design feature, scope, requirements.
The English summary is being prepared. Showing the original description.
Open or update a draft PR for the current branch. Use when: create PR, open PR, draft PR, pull request, prepare for review.
The English summary is being prepared. Showing the original description.