phxtriage

# 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 review ``` ## Why Triage After `/phx:review` produces findings, you have three options: 1. **Fix everything** — `/phx:plan .claude/plans/{slug}/reviews/...` 2. **Triage first** — `/phx:triage` (filter, then fix what matters) 3. **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}" ...