oliver-kriska/phx:triage
plugins/elixir-phoenix/skills/triage/SKILL.md
Triage review findings interactively — approve, skip, or prioritize each issue. Use after /phx:review to filter findings before fixing.
$ install --global
skillsauthnpx skillsauth add oliver-kriska/claude-elixir-phoenix phx:triageInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 7, 2026, 8:07 PM4.8s2 files scanned
SKILL.md
- name:
- phx:triage
- description:
- Triage review findings interactively — approve, skip, or prioritize each issue. Use after /phx:review to filter findings before fixing.
- effort:
- low
- argument-hint:
- [path to review file]
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:
- 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:compound
References
${CLAUDE_SKILL_DIR}/references/triage-patterns.md— Common triage decisions
Related Skills
oliver-kriska/phx:verify
development
VerifiedTrustedCommunity
Verify Elixir/Phoenix changes — compile, format, and test in one loop. Use after implementation, before PRs, or after fixing bugs.
405SKILL.mdUpdated Apr 7, 2026
oliver-kriska/elixir-idioms
development
VerifiedTrustedCommunity
OTP/BEAM patterns and Elixir idioms — GenServer, Supervisor, Task, Registry, pattern matching, with chains, pipes. Use when designing processes or debugging BEAM issues.
405SKILL.mdUpdated Apr 7, 2026
oliver-kriska/lab:autoresearch
tools
VerifiedTrustedCommunity
Self-improving loop for plugin skills. Reads program.md, proposes one mutation per iteration, evaluates against deterministic scorer, keeps improvements via git, reverts failures. Targets weakest skill+dimension. Use with /loop for overnight runs.
340SKILL.mdUpdated Apr 7, 2026
oliver-kriska/phx:audit
development
VerifiedTrustedCommunity
Project health audit and health check — architecture, performance, tests, dependencies, code quality. Use when assessing overall project health, before releases, or after refactors.
339SKILL.mdUpdated Apr 7, 2026