systematic-debug
Skill209 starsChanged 3 months agoMITView on GitHub
4-phase root cause analysis and debugging
4 other projects use a version of this.
Adopted by
Most recently taken up by
- RndmCodeGuy20/ordnancetheir own version, first seen Aug 25, 2026
- asynkron/asynkron-skillstheir own version, first seen Jul 14, 2026
- mark2685/agent-toolstheir own version, first seen Jun 12, 2026
- anshul-garg27/claude-enhancement-suitetheir own version, first seen Mar 10, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- asynkron/asynkron-skills★ 32same name
- anshul-garg27/claude-enhancement-suite★ 0same name
- mark2685/agent-tools★ 0same name
- RndmCodeGuy20/ordnance★ 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.
- AGENTS.mdAGENTS.md
- backup-skillSkill
- brainstormingSkill
- code-reviewSkill
- content-draftSkill
- cost-analyticsSkill
- daily-standupSkill
- devops-auditSkill
- goal-plannerSkill
- heartbeatSkill
- meeting-minutesSkill
- memory-consolidationSkill
- project-plannerSkill
- research-synthesisSkill
- tdd-cycleSkill
- _templateSkill
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 4 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 25
Update learnings.md with debugging insights
- Distinctive: line 28
If 3 fix attempts fail, trigger architectural review
- Distinctive: line 29
Never apply workaround without understanding root cause
“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.
Files
Systematic Debugging
Description
Four-phase debugging methodology: reproduce, investigate, fix, verify. Prevents guesswork and ensures root cause is found before any fix is applied.
When to Use
- Encountering a bug or error
- System failure or crash
- Unexplained behavior
- Performance regression
Process
- Reproduce: Capture exact steps, environment, and error output
- Investigate: Trace root cause through logs, stack traces, and code analysis
- Fix: Apply minimal fix addressing root cause (not symptoms)
- Verify: Confirm fix resolves the issue and doesn't introduce regressions
- Update learnings.md with debugging insights
Safety
- If 3 fix attempts fail, trigger architectural review
- Never apply workaround without understanding root cause
Output
Debug report: symptoms, root cause, fix applied, verification results
Agent Assignment
- Primary: opencode
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.