debug
Skill1 starsChanged 4 days agoMITView on GitHub
Find and fix the root cause of a bug, a failing test, a broken build or unexpected behavior, with a test that proves it stays fixed. Use when something errors, crashes, hangs, regresses, behaves differently than expected, or "worked yesterday".
191 other projects use a version of this.
Adopted by
Most recently taken up by
- champ18ion/claud18codetheir own version, first seen Nov 16, 2026
- jestermaxdelta/roblox-building-skilltheir own version, first seen Nov 16, 2026
- chuckplayer/claude-agent-packtheir own version, first seen Nov 16, 2026
- automagik-dev/omnitheir own version, first seen Nov 15, 2026
- patrickjaja/claude-desktop-extratheir own version, first seen Nov 15, 2026
- NVIDIA/Model-Optimizertheir own version, first seen Nov 15, 2026
Used with
Projects with it also use add-discord, add-slack and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
MicrosoftSkilladd-discord
Add Discord bot channel integration via Chat SDK.
Also in 11 projects that use this
MicrosoftSkilladd-slack
Add Slack channel integration via Chat SDK.
Also in 11 projects that use this
- +10 more from microsoft
Other versions191 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 191
- Yeachan-Heo/oh-my-claudecode★ 41ksame name
- Yeachan-Heo/oh-my-claude-sisyphus★ 41ksame name
- anthropics/knowledge-work-plugins★ 36ksame name
- gavrielc/nanoclaw★ 31ksame name
- nanocoai/nanoclaw★ 31ksame name
- qwibitai/nanoclaw★ 31ksame name
- openai/symphony★ 27ksame name
- FalkorDB/FalkorDB★ 11ksame name
- NVIDIA/Model-Optimizer★ 5.6ksame name
- NVIDIA/TensorRT-Model-Optimizer★ 5.6ksame name
181 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository20 other files it gives its agents.
- AGENTS.mdAGENTS.md
- agents-mdSkill
- app-iconSkill
- buildSkill
- cloneSkill
- design-systemSkill
- docker-optimizeSkill
- improve-loopSkill
- mac-appSkill
- mac-designSkill
- product-briefSkill
- quality-barSkill
- refactorSkill
- researchSkill
- reviewSkill
- start-hereSkill
- stop-overthinkingSkill
- ui-directorSkill
- user-storiesSkill
- ux-designSkill
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 8 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 176 edited versions we read keep these.
8
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Stop changing code. Write the exact steps, input and environment that show the bug, and make it happen on demand: a failing test, a script, …
- Distinctive: line 20
Read the whole error and the first one first.
- Distinctive: line 21
Read the stack trace to the line in your code, then read that code and its callers.
- Distinctive: line 22
Check what changed: git log, git diff, dependency updates, config, data.
- Distinctive: line 32
Ask "why" until you reach a cause that, fixed, makes the symptom impossible, not just unlikely.
- Distinctive: line 37
Write the test that reproduces the bug.
- Distinctive: line 41
Remove debug logging and experiments.
- Distinctive: line 45
If the bug came from a pattern, check the codebase for other instances of it.
- Very specific: line 46
When the project keeps a fix log (docs/FIXLOG.md), add: symptom, cause, fix, and a last line Rule: <what to always or never do>.
“Common” is measured: kept by at least 6 in 10 of the 176 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Debug
The outcome: the real cause is found and fixed once, where every caller benefits, with a test that failed before the fix and passes after. Not a symptom patched in the one place the report named.
1. Stop and reproduce
Stop changing code. Write the exact steps, input and environment that show the bug, and make it happen on demand: a failing test, a script, or a command. A bug you can't reproduce, you can't prove fixed. If it only happens sometimes, find what makes it happen more (load, timing, data).
2. Read the evidence
- Read the whole error and the first one first; later errors often come from it.
- Read the stack trace to the line in your code, then read that code and its callers.
- Check what changed:
git log,git diff, dependency updates, config, data. When it worked yesterday,git bisectfinds the commit. - Logs, network requests, the database state. Add logging where you lack evidence, and remove it after.
3. Find the cause
- Form one hypothesis at a time and test it with the smallest experiment that can prove it wrong. Write down what you ruled out.
- Narrow the space: halve the input, the code path or the history until the cause is isolated.
- Ask "why" until you reach a cause that, fixed, makes the symptom impossible, not just unlikely.
- Grep every caller of the function you suspect. The same bug often lives in sibling paths.
4. Fix it once
- Write the test that reproduces the bug. It fails.
- Fix the cause in the shared code, so every caller benefits. Keep the fix as small as it can be while being complete.
- The test passes, and so does the whole relevant suite.
- Remove debug logging and experiments.
5. Guard it
- If the bug came from a pattern, check the codebase for other instances of it.
- When the project keeps a fix log (
docs/FIXLOG.md), add: symptom, cause, fix, and a last lineRule: <what to always or never do>. A rule that applies to every agent goes inAGENTS.md.
Never
- Change code at random until the symptom goes away.
- Silence the error: an empty catch, a suppression comment, a skipped test, a retry around a bug.
- Loosen a test or a constraint to make it pass.
- Declare it fixed without running the reproduction again.
Done when
The cause is named in one sentence, the fix is in the shared code, a test that failed before now passes, the full suite passes, and the original steps no longer show the bug.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

