workflow-bug-triagelisted

Use when investigating a bug to root-cause and FILE a GitHub issue rather than fixing immediately — counterpart to /swe-workbench:debug (which patches). Enforces the Iron Law (no patches without root cause), runs a 4-phase loop (Investigation, Pattern Analysis, Hypothesis, File issue), and produces a structured issue with code-path table and impact assessment.
lugassawan/swe-workbench · ★ 2 · AI & Automation · score 71

Install: claude install-skill lugassawan/swe-workbench

# Workflow: Bug Triage (investigate + file issue) **Announce at start:** "I'm using the workflow-bug-triage skill to investigate the root cause and file a GitHub issue." ## When to invoke - The user describes a bug, defect, or unexpected behaviour and wants it documented (not fixed in-session). - Phrases: "investigate this bug", "find the root cause", "file an issue for this bug", "triage this". - The bug is in code the user does not own, or fix-planning needs to happen separately. - The investigation needs to produce a shareable artifact (an issue) other people will act on. ## When NOT to invoke - The user wants a fix **now** → use `/swe-workbench:debug` (counterpart skill that ends in code change + regression test). - The root cause is already known and only the fix is needed → use `/swe-workbench:debug`. - The user is capturing a feature request, idea, or improvement (not a bug) → use the `/capture` command directly. - The user is reviewing already-merged code for retroactive issues → use `/swe-workbench:review` first. ## Iron Law **NO FIXES WITHOUT ROOT CAUSE FIRST.** If the user proposes a fix before the root cause is established, refuse politely: > "I'd like to find the root cause before suggesting a fix — otherwise we risk piling band-aids on a deeper issue. Can I run the investigation first?" Red flags that mean STOP investigating-by-fixing and return to Phase 1: - "Quick fix for now…" - "Just try changing X…" - "It's probably X, let me patch it." - "Let me