Triage — Interactive Review Resolution
Walk through review findings one by one for human decision before committing to fixes.
Usage
/phx:triage .claude/plans/user-auth/reviews/user-auth-review.md
/phx:triage # Uses most recent reviewWhy Triage
After /phx:review produces findings, you have three options:
- Fix everything —
/phx:plan.claude/plans/{slug}/reviews/... - Triage first —
/phx:triage(filter, then fix what matters) - Handle manually — Read review, pick what to fix yourself
Best when review has 5+ findings and you want to prioritize.
Workflow
Step 1: Load Review
Read the review file. Parse all findings with severity.
Auto-approve Iron Law violations: Findings matching the 13 Iron Laws are auto-approved as "Fix it" without asking. These are non-negotiable in Elixir/Phoenix development.
Step 2: Present ALL Findings for Batch Selection
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)"
header: "Triage"
multiSelect: true
options:
- label: "All BLOCKERs ({count})"
description: "Fix all critical issues"
- label: "All WARNINGs ({count})"
description: "Fix all should-fix issues"
- label: "[BLOCKER] {title 1}"
description: "{file}:{line} — {brief description}"
- label: "[WARNING] {title 2}"
description: "{file}:{line} — {brief description}"If >4 options, batch into groups of 4 with severity shortcuts in the first batch. Severity shortcuts select all findings of that level — user can mix shortcuts with individual picks.
Step 3: Gather Context on Selected Items
For selected items, ask ONE batch follow-up: "Any specific approach for any of these?" If they say "just fix them", proceed.
Step 4: Generate Triage Summary
Write to .claude/plans/{slug}/reviews/{slug}-triage.md with Fix Queue (approved items with checkboxes), Skipped, and Deferred sections.
Step 5: Present Next Steps
Triage complete: {n} to fix, {n} skipped, {n} deferred.
1. Plan fixes — /phx:plan .claude/plans/{slug}/reviews/{slug}-triage.md
2. Fix directly — /phx:work (for simple fixes)
3. Review deferred items later
4. Capture solutions — /phx:compound (if patterns were solved)Iron Laws
- Batch selection over one-by-one — Use multiSelect for efficiency
- User decides, not the agent — Present facts, don't push
- BLOCKERs cannot be skipped silently — Warn if user tries
- Capture user context — Every "fix it" should include any user guidance for better fixes
- Suggest compound after triage — If triage reveals solved patterns (root cause identified, fix known), mention
/phx:compound - NEVER auto-decide severity or auto-dismiss findings — the human assigns final priority; present the agent's severity as a recommendation, not a verdict
Integration with Workflow
/phx:review
|
/phx:triage ← YOU ARE HERE (interactive filtering)
|
/phx:plan (with triage file) → /phx:work → /phx:compoundReferences
${CLAUDE_SKILL_DIR}/references/triage-patterns.md— Common triage decisions