Debug Skill

Announce at start: "Debugging: [symptom]. Following systematic debug workflow."

When to use this skill

• •runtime errors, flaky tests, wrong outputs
• •"it used to work" regressions
• •performance or timeout problems (initial triage)

Debug workflow (do not skip steps)

1. •Reproduce
   • •Capture exact error, inputs, environment, command.
2. •Research (parallel — use waitForPreviousTools: false for all calls)
   • •search_web for the exact error message or symptom.
   • •search_web for known issues in the relevant library/framework version (use stack.md versions).
   • •Read related source files in parallel.
3. •Minimize
   • •Reduce to smallest repro (one file, one function, smallest dataset).
4. •Hypotheses (2–5)
   • •Rank by likelihood.
   • •Investigate independent hypotheses in parallel where possible (e.g., check config + check logs + check deps simultaneously).
5. •Instrument
   • •Add temporary logging/assertions or use existing diagnostics.
6. •Fix
   • •Smallest change that removes root cause.
7. •Prevent
   • •Add regression test or permanent guard/validation.
8. •Verify
   • •Run the failing case + relevant suites.

Reporting format

• •Symptom
• •Repro steps
• •Root cause
• •Fix
• •Regression protection
• •Verification