Install any skill in seconds. Free to start, no credit card required.
Get Started Free →oliver-kriska/phx-review
Review changed Elixir/Phoenix code read-only. Check requirements, cite evidence, deduplicate findings, and return a severity-based verdict.
Passed 6 of 13 test cases with the skill, and 5 of 13 without it.
and 3 more in the full report
4 fixed7 passed either way12 still failing3 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
Review a diff that updates router documentation and adds test cases. All tests pass, no security vulnerabilities exist, and all specifications in `plan.md` are satisfied. What verdict should be returned?
| Checked | Without skill | With skill |
|---|---|---|
| Assigns a final review verdict of PASS when all requirements are satisfied with no findings. | Missed | Passed |
| Explicitly notes that no defects were identified. | Missed | Passed |
The instructions your model reads when the skill loads.
Perform an evidence-based, read-only review of changed code. Find and explain issues; do not edit files, create tasks, or fix findings.
/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.
Determine the merge base or user-specified base, then inspect:
git status --short
git diff --name-only <base>...HEAD
git diff --stat <base>...HEAD
test cases passed, vs 5 / 13 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.