debug
Skill0 starsChanged 8 months agoMITView on GitHub
Debug errors with systematic 6-step protocol. Paste error message or describe the bug.
192 other projects use a version of this.
Adopted by
Most recently taken up by
- PeanutGT/NutsSkillstheir own version, first seen Nov 8, 2026
- jskswamy/skillstheir own version, first seen Nov 8, 2026
- Firzus/agent-skillstheir own version, first seen Nov 8, 2026
- domengabrovsek/agent-configtheir own version, first seen Nov 8, 2026
- domengabrovsek/claudetheir own version, first seen Nov 8, 2026
- microsoft/veronatheir own version, first seen Nov 8, 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
- MicrosoftSkill
add-slack
Add Slack channel integration via Chat SDK.
Also in 11 projects that use this
- +10 more from microsoft
Other versions192 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 192
- Yeachan-Heo/oh-my-claude-sisyphus★ 41ksame name
- Yeachan-Heo/oh-my-claudecode★ 41ksame name
- anthropics/knowledge-work-plugins★ 35ksame name
- gavrielc/nanoclaw★ 31ksame name
- nanocoai/nanoclaw★ 31ksame name
- qwibitai/nanoclaw★ 31ksame name
- openai/symphony★ 27ksame name
- FalkorDB/FalkorDB★ 10ksame name
- NVIDIA/TensorRT-Model-Optimizer★ 5.6ksame name
- NVIDIA/Model-Optimizer★ 5.6ksame name
182 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 repository19 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- commitSkill
- consolidate-learningsSkill
- dailySkill
- handoffSkill
- init-projectSkill
- learnings-loopSkill
- optimizeSkill
- planSkill
- project-detectorSkill
- quick-researchSkill
- reflectSkill
- reviewSkill
- scaffoldSkill
- session-memorySkill
- strategic-compactSkill
- teachSkill
- testSkill
- wrapSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 7 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 175 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 22
Use subagents to search for relevant code: the error source, related modules, tests
- Distinctive: line 30
Test the most likely hypothesis FIRST
- Distinctive: line 31
Use targeted reads, not full-file scans
- Distinctive: line 32
Check git blame if the code worked before: when did it break?
- Distinctive: line 36
NEVER change code you don't understand hoping it fixes things
- Distinctive: line 39
Run tests to verify the fix
- Distinctive: line 40
Check for regressions in related functionality
“Common” is measured: kept by at least 6 in 10 of the 175 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
Error/Bug Report
$ARGUMENTS
Current State
!git branch --show-current 2>/dev/null
!git diff --stat 2>/dev/null | head -10
Debugging Protocol — Follow these steps IN ORDER:
Step 1: Reproduce
- Identify the exact trigger for the error
- Note the full stack trace and error message
Step 2: Isolate
- Use subagents to search for relevant code: the error source, related modules, tests
- Identify the smallest possible scope where the bug lives
Step 3: Hypothesize
- Form 2-3 hypotheses about root cause
- List evidence for/against each
Step 4: Verify
- Test the most likely hypothesis FIRST
- Use targeted reads, not full-file scans
- Check git blame if the code worked before: when did it break?
Step 5: Fix
- Make the minimal change that fixes the root cause (not symptoms)
- NEVER change code you don't understand hoping it fixes things
Step 6: Confirm
- Run tests to verify the fix
- Check for regressions in related functionality
- Explain what caused the bug and why the fix works
IMPORTANT: If you've tried the same approach twice and it didn't work, STOP and try a fundamentally different strategy.
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.