debug-session
Skill16 starsChanged 7 months agoMITView on GitHub
Structured debugging flow for any bug or unexpected behavior. Follows reproduce, isolate, hypothesize, fix, verify, log. Triggers on \"debug session\", \"can't figure out why\", \"weird behavior\", \"something's wrong with\", \"why is X not working\", \"help me debug\".
6 other projects use a version of this.
Adopted by
Most recently taken up by
- jars-demo/jars-skillstheir own version, first seen Oct 25, 2026
- manastalukdar/ai-devstudiotheir own version, first seen Oct 13, 2026
- ai-dynamo/dynamotheir own version, first seen Oct 8, 2026
- joris887/exosuittheir own version, first seen Aug 20, 2026
- pathorsAI/skillstheir own version, first seen Jul 20, 2026
- SpencerGoss/agent-engineeringtheir own version, first seen Jun 18, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- ai-dynamo/dynamo★ 8.5ksame name
- joris887/exosuit★ 9same name
- manastalukdar/ai-devstudio★ 1same name
- jars-demo/jars-skills★ 0same name
- pathorsAI/skills★ 0same name
- SpencerGoss/agent-engineering★ 0same name
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 repository45 other files it gives its agents.
- AGENTS.mdAGENTS.md
- docs/agents.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- actSkill
- security-checkSkill
- environment-checkSkill
- run-verificationSkill
- refactorSkill
- debug-session-archivedSkill
- generate-guardsSkill
- check-anthropicSkill
- code-reviewerSkill
- code-reviewSkill
- end-sessionSkill
- evolve-checkSkill
- evolveSkill
- fix-bugSkill
- forgetSkill
- frontend-designSkill
- guardSkill
- kit-healthSkill
- learnSkill
- map-codebaseSkill
- modeSkill
- parallel-prototypesSkill
- planSkill
- powershell-safeSkill
- product-riskSkill
- progress-reportSkill
- prototype-hypothesisSkill
- recallSkill
- refactoring-uiSkill
- scan-codebaseSkill
- scan-conventionsSkill
- search-firstSkill
- search-memorySkill
- shadow-codeSkill
- skill-creatorSkill
- smart-resumeSkill
- start-sessionSkill
- strategic-compactSkill
- tourSkill
- ux-heuristicsSkill
- verification-loopSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
3
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 12
Allowed Tools: Read, Grep, Glob, Bash, Edit, Write
- Distinctive: line 40
Never skip the reproduce step.
- Distinctive: line 42
If the fix doesn't work, go back to step 2, not step 4.
“Common” is measured: kept by at least 6 in 10 of the 6 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
Skill: debug-session
Trigger: "debug session", "can't figure out why", "weird behavior", "something's wrong with", "why is X not working", "help me debug"
Description: Structured debugging flow for any bug or unexpected behavior. Follows reproduce, isolate, hypothesize, fix, verify, log.
Allowed Tools: Read, Grep, Glob, Bash, Edit, Write
Steps
- Reproduce — confirm the bug exists. Ask the user to describe exact steps. Run the failing scenario if possible.
- Isolate — narrow down where the bug lives:
- Which file? Grep for the relevant function/variable.
- Which line? Read the suspect code.
- What changed recently? Check git log or ask the user.
- Hypothesize — state ONE clear hypothesis: "I think X is happening because Y."
- Fix — apply the minimal fix. Follow plan-before-edit if the project has that rule.
- Verify — confirm the fix works. Run the scenario again.
- Log — update error-lookup.md (if it exists) with:
So the same bug never costs time again.| Symptom | Root cause | Fix | Date |
Notes
- Never skip the reproduce step. "I think I know what's wrong" without reproducing leads to wrong fixes.
- One hypothesis at a time. Don't shotgun 3 changes and hope one works.
- If the fix doesn't work, go back to step 2, not step 4.
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.