phx-review
Review changed Elixir/Phoenix code read-only. Check requirements, cite evidence, deduplicate findings, and return a severity-based verdict.
npx skills add oliver-kriska/claude-elixir-phoenix --skill phx-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 Perform an evidence-based, read-only review of changed code. Find and explain issues; do not edit files, create tasks, or fix findings. ## Usage ```text phx-review phx-review test phx-review security phx-review .claude/plans/auth/plan.md phx-review --no-requirements ``` Treat the text after the skill name as a focus area, issue identifier, or path to a plan/specification. ## Iron Laws 1. **Review is read-only** — inspect and report; never modify the worktree. 2. **Scope to changed code** — distinguish new defects from pre-existing issues. 3. **Every finding needs evidence** — cite a path and line, explain impact, and describe the concrete failure mode. 4. **Check requirements when available** — unmet requirements affect the verdict. 5. **Deduplicate and prioritize** — one root cause is one finding, with the highest justified severity. 6. **Do not require custom agents, hooks, MCP, or unavailable task APIs** — use optional runtime capabilities only when present. ## Workflow ### 1. Establish Scope Determine the merge base or user-specified base, then inspect: ```bash git status --short git diff --name-only <base>...HEAD git diff --stat <base>...HEAD git d
- Usage
- Iron Laws
- Workflow
- 1. Establish Scope
- 2. Load Requirements
- 3. Review by Concern
- 4. Verify Findings
- 5. Report a Verdict
- References
git status --short git diff --name-only <base>...HEAD git diff --stat <base>...HEAD git diff <base>...HEAD -- <changed-files>
What does the phx-review skill do?
Review changed Elixir/Phoenix code read-only. Check requirements, cite evidence, deduplicate findings, and return a severity-based verdict.
How do I install it?
Run `npx skills add oliver-kriska/claude-elixir-phoenix --skill phx-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.