debug · pwguler — Claude Code skill: what it does, how to install
debug is a Claude Code and Cursor skill that traces bug root causes step by step and verifies regression tests.
MIT 1,000 installs ★ 10 updated 2026-10-16
npx skills add pwguler/skills --skill debug -a claude-codeWhat debug does
The agent builds a task list to isolate the root cause, creates a minimal reproduction, and tests hypotheses before editing code. Dead code gets removed from modified files prior to the fix. A regression test is added once the issue is resolved.
The process halts after three consecutive invalid hypotheses or when reproduction data is missing. The rule triggers on mentions of errors, bugs, or failing tests.
What it helps with
- find root cause of a bug step by step
- build minimal reproduction for failure
- add regression test for a fix
- remove dead code before editing
Example prompts for the agent
- Fix the bug in the auth module
- The test is failing unexpectedly, investigate
- The code is broken after update
How to install debug
1Skills CLI (Vercel)
npx skills add pwguler/skills --skill debug -a claude-code2Manually: put the files in place
~/.claude/skills/debug/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/debug/
1Skills CLI (Vercel)
npx skills add pwguler/skills --skill debug -a codex2Manually: put the files in place
.agents/skills/debug/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add pwguler/skills --skill debug -a cursor2Manually: put the files in place
.cursor/skills/debug/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install pwguler/skills skills/debug2Manually: put the files in place
.github/skills/debug/SKILL.md1Skills CLI (Vercel)
npx skills add pwguler/skills --skill debug -a gemini-cli2Platform CLI
gemini skills install https://github.com/pwguler/skills --path skills/debugManually: put the files in place
.devin/skills/debug/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add pwguler/skills --skill debug -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about debug
How to install debug in Claude Code?
Run npx skills add pwguler/skills --skill debug -a claude-code followed by ~/.claude/skills/debug/SKILL.md.
What does debug do?
Finds the primary cause of a bug, builds a reproduction test, checks hypotheses, and adds a regression test after fixing.
When does the skill trigger?
The agent activates the skill when you mention a bug, error, broken code, or when a test fails unexpectedly.
Source text
SKILL.md · MIT
--- name: debug description: Find the root cause of a bug before you fix it. Read this skill before you fix any bug. Read it also when the fix looks obvious. Use it when the user says "fix", "broken", "not working", "error", "failing", or "bug". Use it also when a test fails unexpectedly during other work. --- Do not fix a bug before you know its root cause. The search starts at the symptom, but it does not end there. Fast path: when the error output shows the first cause directly, skip the hypothesis steps. An example is a stack line that points at the cause. Do not skip the reproduction, the regression test, or the `verify` skill in step 8. If the visible fix does not make the reproduction pass on the first try, the cause was not visible. Then do all the steps. 1. Before you reproduce the bug, create a task list with these steps as its items. If a task list already exists, add the steps to it. Each step is one item. When you skip a step, mark it done and add `skip: <reason>` to its text. The fast path skips the hypothesis steps this way. To go back to an earlier step, add that step and each step after it again as new items. Then delete the unfinished items that the new items replace. 2. Reproduce the bug first. Build the smallest reproduction that fails every time. If you cannot reproduce the bug, collect evidence until you can: logs, inputs, and versions. Do not guess. 3. Read the actual error. Find the first cause in the chain of causes, not the nearest symptom. 4. Make one hypothesis. Write it with the observation that would confirm it or refute it. Get that observation before you start a fix: a log line, an assertion, or a probe. If the evidence does not exist yet, add instrumentation. Keep the instrumentation small and easy to remove, and remove it when it has given its answer. 5. When two hypotheses compete, design one observation that shows which one is true. Do not try fixes one after another. 6. Fix the root cause, one fix at a time. Flag another problem that you find, such as a second bug, but do not fix it. Dead code is not another problem. Before the fix, delete the dead code in each file that the fix changes, as `implement` does. Do this also when the bug did not touch that code. Dead code is functions, imports, and parameters that no caller uses, and branches that no caller reaches. It is also stale flags, and validators that repeat a check that a boundary already did. It is also comments that repeat the code or excuse a workaround. Keep dead code that a non-goal puts out of scope. Read [fix root causes](references/fix-root-causes.md) before a fix that adds a guard, a catch, or a comment that defends it. Read it also when the same cause can occur elsewhere, or when the failure shows only after a restart. 7. Add the regression test that would have caught this bug. It fails on the old code and passes with the fix. 8. Before you report the fix, read the `verify` skill and follow it. Your report claims that the bug is fixed, and `verify` proves that claim. When the bug appeared inside a slice, the full gate waits for the slice's commit. Rules: - Do not try several fixes at random to see if one helps. - Stop the loop after three refuted hypotheses in a row. Stop it also when the available evidence cannot give a reproduction. Then report what you tried and which observation is missing, and let the user decide. - If the fix does not make the reproduction pass, the hypothesis was wrong. Go back to step 4. Do not keep the failed fix and add a second fix. When two failed fixes shared one premise, read [attack the premise](references/attack-the-premise.md). - If the root cause shows a design problem, say so. Offer to run `drill` on the redesign. Do not hide the problem under a workaround. - When the cause took more than one hypothesis to find, propose a cheap signal that stays on. It is a log line, a metric, or an assertion that would have shown this cause at once. Add it when the user agrees.
© pwguler · MIT · pwguler/skills
Similar skills
All skills for Agent setup: memory, context, orchestration →debug by other authors comes first.