# 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.

- Skill: `kroshank/debugger-assistant` (Agent Skill)
- Install (CLI): `npx skillmds@latest add kroshank/debugger-assistant`
- Raw SKILL.md: https://api.skillmd.com/api/skills/kroshank/debugger-assistant/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: KRoshanK (https://skillmd.com/u/kroshank)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/kroshank/debugger-assistant

---


# 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