Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →oliver-kriska/triage
Triage review findings interactively — approve, skip, or prioritize each issue. Use after /phx:review to filter findings before fixing.
Passed 11 of 16 test cases with the skill, and 3 of 16 without it.
and 12 more in the full report
11 fixed4 passed either way7 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
What exact question should be asked when prompting for custom approach guidance after findings are selected during review triage?
| Checked | Without skill | With skill |
|---|---|---|
| Phrases the context prompt as Any specific approach for any of these?. | Missed | Passed |
The instructions your model reads when the skill loads.
Walk through review findings one by one for human decision before committing to fixes.
/phx:triage .claude/plans/user-auth/reviews/user-auth-review.md
/phx:triage # Uses most recent review
After /phx:review produces findings, you have three options:
/phx:plan .claude/plans/{slug}/reviews/.../phx:triage (filter, then fix what matters)Best when review has 5+ findings and you want to prioritize.
Read the review file. Parse all findings with severity.
Auto-approve Iron Law violations: Findings matching any Iron Law are auto-approved as "Fix it" without asking. These are non-negotiable in Elixir/Phoenix development.
Use AskUserQuestion with multiSelect: true. Start with
severity shortcuts, then list individual findings:
AskUserQuestion:
question: "Which findings do you want to fix? (Iron Law violations auto-included)"
test cases passed, vs 3 / 16 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.