debugging-code
Skill1 starsChanged 5 months agoNo licenceView on GitHub
Evidence-first debugging discipline. Use on EVERY bug, error, crash, stack trace, regression, flaky test, or "this stopped working" report, in any language, BEFORE proposing any fix. Also use when a previous fix didn't hold. Enforces reproduce, isolate, root cause, verify, and searching the project's own history before re-deriving anything. Composes with project playbooks like minecwaft-teavm and supersedes generic structured-debugging workflows; apply without being asked.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- JetBrains/rider-skillstheir own version, first seen Oct 14, 2026
- Antthonyyy/marketing-agents-kittheir own version, first seen Oct 13, 2026
- AlmogBaku/debug-skilltheir own version, first seen Oct 8, 2026
- JetBrains/skillstheir own version, first seen Apr 28, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- JetBrains/skills★ 386same name
- AlmogBaku/debug-skill★ 328same name
- JetBrains/rider-skills★ 40same name
- Antthonyyy/marketing-agents-kit★ 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 repository2 other files it gives its agents.
- capturing-knowledgeSkill
- writing-codeSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 4 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.
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.