debugging-master
Skill0 starsChanged 7 months agoNo licenceView on GitHub
A systematic protocol for bugs that don't give up after the obvious fix. Forces root-cause thinking, hypothesis-driven debugging, and minimum-reproduction isolation before any fix lands. Use when the bug is intermittent, spans multiple components, seems to contradict the code, or has already been "fixed" once and came back. Prevents the guess-and-check spiral that burns tokens and confidence. Composes with ultra-efficient.
In this repository19 other files it gives its agents.
- api-designerSkill
- codebase-explorerSkill
- code-reviewSkill
- data-analystSkill
- database-architectSkill
- deep-researchSkill
- dependency-auditorSkill
- documentation-writerSkill
- git-workflowSkill
- human-voiceSkill
- incident-responseSkill
- performance-tuningSkill
- prompt-architectSkill
- refactor-safeSkill
- security-auditSkill
- system-architectSkill
- test-engineerSkill
- ultra-efficientSkill
- ultra-planningSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
20 rules. About 0 are common, 19 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈19
Distinctive · estimate
This author's own choices. Worth a look.
1
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 an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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.