debug-systematic
Skill1 starsChanged 41 days agoMITView on GitHub
Debug failures with a hypothesis-driven loop. Use when fixing bugs, investigating exceptions, flaky tests, or unexpected behavior.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- manastalukdar/ai-devstudiotheir own version, first seen Oct 13, 2026
- travisjneuman/.claudetheir own version, first seen Feb 25, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- travisjneuman/.claude★ 106same name
- manastalukdar/ai-devstudio★ 1same 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 repository49 other files it gives its agents.
- accessibilitySkill
- address-feedbackSkill
- agent-disciplineSkill
- agent-handoffSkill
- api-designSkill
- architecture-decisionSkill
- brainstormSkill
- browser-verifySkill
- code-reviewSkill
- containerizeSkill
- context-efficientSkill
- create-prSkill
- database-changesSkill
- dependency-upgradeSkill
- docs-groundedSkill
- error-handlingSkill
- explore-codebaseSkill
- fix-ciSkill
- frontend-designSkill
- git-commitSkill
- git-worktreeSkill
- incident-triageSkill
- incremental-slicesSkill
- legacy-changeSkill
- migrate-codeSkill
- minimal-diffSkill
- observabilitySkill
- parallel-workSkill
- performance-auditSkill
- plan-before-codeSkill
- python-qualitySkill
- react-componentsSkill
- refactor-safeSkill
- release-notesSkill
- security-reviewSkill
- setup-ciSkill
- shell-safetySkill
- ship-checklistSkill
- simplify-codeSkill
- skill-authoringSkill
- skill-routerSkill
- spec-drivenSkill
- tddSkill
- threat-modelSkill
- triage-issuesSkill
- typescript-strictSkill
- verify-workSkill
- write-docsSkill
- write-testsSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
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
Test: run the smallest check that falsifies a hypothesis.
- Distinctive: line 19
Do not spray unrelated changes hoping something works.
- Distinctive: line 21
Prefer logging/assertions at boundaries over shotgun prints.
≈ “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.
Files
Debug Systematic
Loop
- Observe: capture exact symptom, error text, stack, and repro steps.
- Hypothesize: list 1–3 plausible causes ranked by likelihood.
- Test: run the smallest check that falsifies a hypothesis.
- Isolate: binary-search the fault (input, commit, module, line).
- Fix: change the root cause; keep the diff minimal.
- Verify: confirm the original repro is gone; add a regression test when valuable.
Rules
- Do not spray unrelated changes hoping something works.
- Change one variable at a time when experimenting.
- Prefer logging/assertions at boundaries over shotgun prints.
- Record what was tried so the same dead ends are not repeated.
Output
Symptom: ...
Repro: ...
Root cause: ...
Fix: ...
Verification: ...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.