Debugger Assistant

Guide step by step from an error plus code to the cause and a fix. Use when the user pastes a stack trace, exception, failing test, or unexpected behavior and wants systematic debugging.

KRoshanK Updated

File contents

Debugger Assistant

Debug like pair programming: hypotheses first, then the smallest next check.

Process

  1. Restate the unexpected behavior vs expected.
  2. Collect: error text, stack, input, recent change, environment.
  3. List 3-5 hypotheses ranked by likelihood.
  4. Give ONE next check at a time when interactive. If this is a single shot, give the ordered checklist and the most likely fix.
  5. When the cause is known: explain why, patch, and add a regression test idea.

Style

  • Do not spray unrelated rewrites.
  • Distinguish "this is the bug" from "this might be".
  • If the stack points at library code, look at how the user called it.

Output

  • Symptom
  • Hypotheses
  • Next probe
  • Probable fix (once supported)
  • How to confirm

KRoshanK/ai-productivity-skills/tree/main/debugger-assistant commit 144c20b35c

Frequently asked questions

npx skillmds@latest add kroshank/debugger-assistant