Rapid bug triage — classify severity and recommend next debugging steps. Use this skill immediately when a user reports a bug, error, crash, or unexpected behavior, even if they just say "something is broken" or "this isn't working." Gives the user a fast P0-P3 severity classification and clear next steps within minutes. Trigger for: bug reports, "why is X failing", "something went wrong", crash reports, error messages the user is confused by.
You are performing rapid triage on a bug report. The goal is fast assessment — not deep analysis. You'll classify severity, form an initial hypothesis, and recommend the right next step in under a few minutes.
If the user hasn't provided enough context, ask for:
Don't ask for more than you need — a brief description is enough to triage.
| Priority | Name | Definition |
|---|---|---|
| P0 | Critical | System unusable, data loss, security breach, production down |
| P1 | High | Major feature broken, significant user impact, no workaround |
| P2 | Medium | Feature impaired, workaround exists, moderate impact |
| P3 | Low | Minor issue, cosmetic, edge case, minimal impact |
Also classify complexity:
Check the symptoms against these common patterns:
| Pattern | Key Indicators |
|---|---|
| Null/undefined reference | TypeError: Cannot read property of undefined, NullPointerException |
| Race condition | Intermittent failures, order-dependent, works in debug not prod |
| Memory leak | Gradually growing memory, GC pressure, OOM over time |
| Off-by-one error | ArrayIndexOutOfBounds, missing first or last element |
| Type mismatch | Unexpected coercion, failed validation, serialization errors |
| Resource exhaustion | Too many open files, connection pool exhausted, thread starvation |
| Deadlock | Application hangs, threads in BLOCKED state |
| SQL injection | Unexpected DB errors, authorization bypasses, malformed query errors |
| Infinite recursion | Stack overflow, Maximum call stack exceeded, app crash |
| Cache staleness | Outdated data shown, changes not reflected |
If the description matches a pattern, name it and explain the typical cause.
Based on complexity:
/debug-agent:debug-root-cause for focused root cause analysis/debug-agent:debug-inspect for full 6-phase Fagan inspection## Quick Debug Triage
**Severity:** P[0-3] ([Critical/High/Medium/Low])
**Complexity:** [Simple/Moderate/Complex]
**Initial Assessment:**
[2-3 sentences: what's likely happening and why]
**Pattern Match:** [Matching pattern name, or "No clear pattern match"]
**Recommended Next Step:**
[Specific action — either an immediate fix suggestion, or which workflow to run next]
**Estimated Effort:** [Quick fix (minutes) / Short investigation (hours) / Full investigation (days)]