How do I install the Debug skill?

Run npx skillmds@latest add s1lver091/debug in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Debug safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Debug?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Debug free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

s1lver091 (@s1lver091) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Debug by s1lver091 — Agent Skill

Name: Debug
Author: s1lver091

File contents

Debugging

Do not guess. Work systematically: reproduce, isolate, hypothesize, verify.

Step 1: Reproduce

Before touching any code, confirm you can reproduce the problem.

What is the exact input or sequence of actions that triggers it?
Is it consistent or intermittent?
Does it happen in all environments or only some?

If you cannot reproduce it, stop and ask for more information.

Step 2: Read the error

If there is an error message or stack trace:

Read the full trace, not just the first line
Find the deepest frame in your own code (not library internals) — that is your starting point
Check what values were in scope at that point

Step 3: Isolate

Narrow down where the problem lives before reading more code.

Add temporary logging or assertions to confirm assumptions about state
Bisect: is the problem in the input, the transformation, or the output?
Check: when did this last work? Use git log and git blame to find recent changes

Step 4: Form a hypothesis

Write one sentence: "I believe X is happening because Y." Do not skip this. It prevents you from randomly changing code and hoping it works.

Step 5: Verify the hypothesis

Find the code that should implement the behavior you described.

Read it carefully
Check the actual values at runtime if possible
Look for edge cases the author may have missed

If your hypothesis is wrong, return to step 3. Do not guess-and-check.

Step 6: Fix

Make the smallest possible change that fixes the root cause.

Do not refactor surrounding code while fixing a bug
Do not fix multiple bugs in one change
After fixing, re-read the change and ask: could this break anything else?

Step 7: Verify the fix

Confirm the original issue no longer reproduces
Check that related behavior still works
If a test was failing, confirm it now passes and no others broke

Report format

Root Cause One sentence: what was actually wrong.

Fix What you changed and why that addresses the root cause.

Files Changed

path/to/file.ts:42 — what changed

Regression Risk Any adjacent behavior that should be tested after this fix.

---name: debugdescription: Systematically diagnose and fix bugs, unexpected behavior, or failing tests. Use when something is broken and the cause is not immediately obvious.---# DebuggingDo not guess. Work systematically: reproduce, isolate, hypothesize, verify.## Step 1: ReproduceBefore touching any code, confirm you can reproduce the problem.- What is the exact input or sequence of actions that triggers it?- Is it consistent or intermittent?- Does it happen in all environments or only some?If you cannot reproduce it, stop and ask for more information.## Step 2: Read the errorIf there is an error message or stack trace:- Read the full trace, not just the first line- Find the deepest frame in your own code (not library internals) — that is your starting point- Check what values were in scope at that point## Step 3: IsolateNarrow down where the problem lives before reading more code.- Add temporary logging or assertions to confirm assumptions about state- Bisect: is the problem in the input, the transformation, or the output?- Check: when did this last work? Use `git log` and `git blame` to find recent changes## Step 4: Form a hypothesisWrite one sentence: "I believe X is happening because Y."Do not skip this. It prevents you from randomly changing code and hoping it works.## Step 5: Verify the hypothesisFind the code that should implement the behavior you described.- Read it carefully- Check the actual values at runtime if possible- Look for edge cases the author may have missedIf your hypothesis is wrong, return to step 3. Do not guess-and-check.## Step 6: FixMake the smallest possible change that fixes the root cause.- Do not refactor surrounding code while fixing a bug- Do not fix multiple bugs in one change- After fixing, re-read the change and ask: could this break anything else?## Step 7: Verify the fix- Confirm the original issue no longer reproduces- Check that related behavior still works- If a test was failing, confirm it now passes and no others broke## Report format**Root Cause**One sentence: what was actually wrong.**Fix**What you changed and why that addresses the root cause.**Files Changed**- `path/to/file.ts:42` — what changed**Regression Risk**Any adjacent behavior that should be tested after this fix.

Frequently asked questions

Debug