From elixir-phoenix
Interactively triages code review findings in Phoenix projects: approve, skip, or prioritize issues via multi-select. Follows /phx:review; auto-approves Iron Law violations; generates fix queue summary.
How this skill is triggered — by the user, by Claude, or both
Slash command
/elixir-phoenix:triageThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Walk through review findings one by one for human decision before
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 the 13 Iron Laws 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)"
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.
For selected items, ask ONE batch follow-up: "Any specific approach for any of these?" If they say "just fix them", proceed.
Write to .claude/plans/{slug}/reviews/{slug}-triage.md with Fix Queue
(approved items with checkboxes), Skipped, and Deferred sections.
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)
/phx:compound/phx:review
|
/phx:triage ← YOU ARE HERE (interactive filtering)
|
/phx:plan (with triage file) → /phx:work → /phx:compound
${CLAUDE_SKILL_DIR}/references/triage-patterns.md — Common triage decisionsnpx claudepluginhub oliver-kriska/claude-elixir-phoenix --plugin elixir-phoenixTriage PR review comments by categorizing them as actionable, false positive, or deferrable, fixing actionable items, and posting a status update.
Structures PR review feedback, code comments, or issue tracker items for verification before implementation. Verifies suggestions against codebase; triages issues into agent-ready or human states.
Orchestrates an autonomous comprehensive review pipeline across health, architecture, security, performance, accessibility, tests, and release-readiness. Supports optional ticket creation for backlog or audit.