with one click
triage-issue
// Bug triage: explores codebase for root cause, files GitHub issue with TDD fix plan. Triggers: triage, investigate bug, fix plan, root cause, file issue, bug report.
// Bug triage: explores codebase for root cause, files GitHub issue with TDD fix plan. Triggers: triage, investigate bug, fix plan, root cause, file issue, bug report.
[HINT] Download the complete skill directory including SKILL.md and all related files
| name | triage-issue |
| description | Bug triage: explores codebase for root cause, files GitHub issue with TDD fix plan. Triggers: triage, investigate bug, fix plan, root cause, file issue, bug report. |
| user-invocable | true |
| effort | high |
| argument-hint | [bug description or symptom] |
| agent | debugger |
| context | fork |
| allowed-tools | Read, Grep, Glob, Bash, Agent |
$ARGUMENTS
Investigate a bug, find root cause, and create a GitHub issue with a TDD fix plan. Mostly hands-off.
/triage-issue [bug description or symptom]
gh issue createGet brief description. If not provided, ask ONE question: "What's the problem you're seeing?"
Do NOT ask follow-up questions. Start investigating immediately.
Use Agent (subagent_type=Explore) to deeply investigate:
| Target | What to look for |
|---|---|
| Manifestation | Where the bug appears (entry points, UI, API) |
| Code path | Trace the flow from trigger to symptom |
| Root cause | Why it fails (not just the symptom) |
| Related code | Similar patterns, adjacent modules, existing tests |
| Recent changes | git log on relevant files |
| Working patterns | Similar code elsewhere that works correctly |
Determine:
Ordered list of RED→GREEN cycles. Each cycle is one vertical slice:
Rules:
Use gh issue create with template below. Share URL immediately.
What was found during investigation:
Do NOT include file paths, line numbers, or implementation details. Describe modules, behaviors, and contracts.
RED: Write test that [expected behavior] GREEN: [Minimal change to pass]
RED: Write test that [next behavior] GREEN: [Minimal change to pass]
REFACTOR: [Cleanup after all tests pass]
gh issue create and share the URL — do not ask the user to review a draft firstgh issue create without --body opens $EDITOR. In automated flows the skill hangs — always pass the body file or inline text.debugger agent explored autonomously but returns a narrative. Parse it for: confirmed hypothesis, code paths, and recent changes. Discard speculation./qa-session first, which returns refined reports this skill can then process/fix directly/architecture-audit/prd-to-issues/debug