debugging-systematically
Skill0 starsChanged 6 months agoNo licenceView on GitHub
Runs a structured root-cause analysis protocol when a bug resists quick fixes. Invoke this skill when the user says "still broken", "tried three times", "I don't know why", "same error", or "still failing". The skill resets all prior assumptions, classifies the error type, traces data flow, proposes five ranked hypotheses with the fastest verification method for each, and enforces a no-repeat-fix rule: Claude may not attempt a second fix for the same hypothesis without verification evidence. Prevents the infinite guess-and-retry loop that wastes sessions and erodes trust.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- Knowledge-Forge-AI/agentic-praxis-grimoiretheir own version, first seen Nov 8, 2026
- jjsizemore/jjskillstheir own version, first seen Nov 1, 2026
- vadimvitvickiy/vv-agent-kittheir own version, first seen Oct 20, 2026
- aaravriyer193/skillstheir own version, first seen Oct 13, 2026
- Samueladewole/claude-skillstheir own version, first seen Oct 13, 2026
- MorganOnGitHub/tackletheir own version, first seen Sep 27, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- dork-labs/dorkos★ 11same name
- Knowledge-Forge-AI/agentic-praxis-grimoire★ 2same name
- aaravriyer193/skills★ 1same name
- jjsizemore/jjskills★ 1same name
- MorganOnGitHub/tackle★ 0same name
- Samueladewole/claude-skills★ 0same name
- vadimvitvickiy/vv-agent-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 repository16 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- auditing-dependenciesSkill
- auto-code-reviewSkill
- contracting-apiSkill
- csrf-reviewSkill
- idea-refinerSkill
- implementation-plannerSkill
- migrating-schemaSkill
- orchestrating-hackathonSkill
- refactoring-safelySkill
- reviewing-securitySkill
- running-retrospectiveSkill
- secure-vibe-codingSkill
- ssrf-reviewSkill
- writing-business-planSkill
- writing-srsSkill
The file
We split this skill into the rules it gives an agent
12 rules. 0 are common, 12 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
12
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 7 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.

