systematic-debugging
Installation
SKILL.md
Systematic Debugging
Use this skill when
- You encounter a failing test, error message, or unexpected behavior
- Multiple fix attempts have failed (2+)
- The symptom is clear but the root cause is unclear
- You feel time pressure to "just try something" or skip investigation
- Behavior changed after recent commits or configuration changes
- A production issue or blocking regression surfaces
- The bug appears intermittent or environment-dependent
- You are about to propose a fix without understanding why the problem exists
Do not use this skill when
- The root cause is already known and validated (move to implementation)
- The fix has already been verified in a test environment (move to validation)
- You are responding to a user's explicit "apply this specific fix" request (acknowledge context first, then validate)
- The issue is documentation-only or labeling (use domain-specific conventions directly)