triage-issue
Installation
SKILL.md
Investigate, find root cause, emit a fix plan shaped as RED-GREEN cycles. Mostly hands-off — minimize user prompts.
Process
1. Capture the problem (one prompt max)
If the user has not already described the bug, ask exactly one question: "What's the problem you're seeing?" Then start investigating. No follow-ups yet.
2. Explore and diagnose
Dispatch an Explore agent. Find:
- Where the bug manifests (entry points, UI, API responses)
- What code path executes (trace the flow)
- Why it fails (root cause, not just symptom)
- Related code (similar patterns, adjacent modules, existing tests)
Use git --no-pager grep -n -C 3 <pattern> and ast-grep run -p '<pattern>' -l <lang> -C 3 for structural traces.