diagnosing-bugs
Skill9 starsChanged 29 days agoNo licenceView on GitHub
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
219 other projects use a version of this, 136 of them edited; 34 of 136 edited versions we compared changed its rules; 16 new projects in the last 4 weeks, against 8 the 4 before.
How people change it
34 of 136 edited versions changed its rules, and some changes recur.
Of the 136 edited versions we compared: 72 keep every rule, 30 are an older text, 34 made changes of their own.
Not in older versions
- If the redacted output is not enough to diagnose the bug, say so and ask the user.missing from 30 of 30
- Write the regression test before the fix, but only if there is a correct seam for it.missing from 1 of 30
Rules people drop
- If the redacted output is not enough to diagnose the bug, say so and ask the user.dropped by 18 of 34
- When exploring the codebase, read
GLOSSARY.md(if it exists) to get a clear mental model of the relevant modules, and check ADRs in the area you're touching.dropped by 15 of 34 - Do not proceed until you have reproduced and minimised.dropped by 13 of 34
- Differential loop. Run the same input through old-version vs new-version (or two configs) and diff outputs.dropped by 11 of 34
- If you catch yourself reading code to build a theory before this command exists, stop: jumping straight to a hypothesis is the exact failure this skill prevents. No red-capable command, no Phase 2.dropped by 11 of 34
- Property / fuzz loop. If the bug is "sometimes wrong output", run 1000 random inputs and look for the failure mode.dropped by 10 of 34
- Debugger / REPL inspection if the env supports it. One breakpoint beats ten logs.dropped by 10 of 34
- If a correct seam exists:dropped by 10 of 34
Rules people add
- No red-capable command, no Phase 2.added by 3 of 34
- If you catch yourself reading code to build a theory before this command exists,added by 3 of 34
- Stop and say so explicitly. List what you tried. Ask the user for: (a) access to whatever environment reproduces it, (b) a captured artifact (HAR file, log dump, screen recording with timestamps), or (c) permission to add temporary instrumentation. …added by 2 of 34
- A rule we can't quote: its licence doesn't allow itadded by 2 of 34
We split this file and each edited version into the rules they give an agent and match them by wording. A version that adds no rule of its own and has not changed since this file last did reads as an older text, so what it lacks is not counted as dropped. We keep no past texts of a file, so that is inferred, and an edited version that started from an older text still counts its gaps as drops.
Adopted by
Rising: 16 new projects took it in the last 4 weeks, 2× the 4 weeks before.
Most recently taken up by
- bamlab/flashlightword for word, first seen Nov 16, 2026
- Floppa2003/skillsword for word, first seen Nov 16, 2026
- endalk200/skillsedited, first seen Nov 16, 2026
- atiq-r/skillsedited, first seen Nov 16, 2026
- devdeepjs/kobayashi-maruedited, first seen Nov 16, 2026
- qelphybox/tg-mcpword for word, first seen Nov 16, 2026
Used with
Projects with it also use decision-mapping.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
FabienDehopreSkilldecision-mapping
Turn a loose idea into a sequenced map of investigation tickets, then drive them to resolution one at a time.
Also in 6 projects that use this
Other versions219 projects use a version of this.
Word for word · 51
- mattpocock/skills★ 325k100% same
- ArcReel/ArcReel★ 6.6k100% same
- withcoral/coral★ 5k100% same
- bamlab/flashlight★ 1.6k100% same
- epam/ketcher★ 939100% same
- mxyhi/ok-skills★ 511100% same
- itsmylife44/cliproxyapi-dashboard★ 285100% same
- tt-a1i/matt-skills-with-to-goal★ 192100% same
- QiYueran-source/waymark★ 112100% same
- alexj11324/Mikka★ 87100% same
41 more not listed
Edited · 136
- The-Vibe-Company/quivr★ 40k99% same
- QuivrHQ/quivr★ 40k99% same
- GreyDGL/PentestGPT★ 16k92% same
- bestofjs/bestofjs★ 3.1k94% same
- getsentry/sentry-react-native★ 1.8k11% same
- mdiri-ai/SoduWork★ 93096% same
- getsentry/sentry-dart★ 87720% same
- moeru-ai/xsai★ 66999% same
- chrisdoc/hevy-mcp★ 54194% same
- aws/graph-explorer★ 492100% same
126 more not listed
Wrote their own version · 32
- vinvcn/mattpocock-skills-zh-CN★ 5.8ksame name
- ChatbotXIO/ChatbotX★ 1.1ksame name
- nodetool-ai/nodetool★ 637same name
- stevesolun/ctx★ 583same name
- devcxl/mattpocock-skills-zh★ 543same name
- OyadotAI/oya-browser★ 349same name
- jellydn/my-ai-tools★ 129same name
- WenWuZhiDao/mattpocock-skills-zh★ 27same name
- rafaelob/pragmatic-agent-skills★ 24same name
- mxrsv/agents-skills★ 11same name
22 more not listed
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 repository60 other files it gives its agents.
- ask-mattSkill
- chief-of-staffSkill
- claude-handoffSkill
- codebase-designSkill
- code-reviewSkill
- domain-modelingSkill
- giclaw-evolveSkill
- git-guardrails-claude-codeSkill
- grillingSkill
- grill-meSkill
- grill-with-docsSkill
- handoffSkill
- implementSkill
- implement-specSkill
- improve-codebase-architectureSkill
- loop-meSkill
- migrate-to-shoehornSkill
- prototypeSkill
- prSkill
- researchSkill
- retroSkill
- scaffold-exercisesSkill
- setup-matt-pocock-skillsSkill
- setup-pre-commitSkill
- setup-ts-deep-modulesSkill
- tddSkill
- teachSkill
- to-questionnaireSkill
- to-specSkill
- to-ticketsSkill
- triageSkill
- wait-whatSkill
- wayfinderSkill
- wizardSkill
- writing-beatsSkill
- writing-for-agentsSkill
- writing-fragmentsSkill
- writing-shapeSkill
- Battle Pass Rewards ClaimSkill
- Claim Achievement RewardsSkill
- Claim Event RewardsSkill
- Claim Mail RewardsSkill
- Collect ExpeditionsSkill
- Genshin Automation PitfallsSkill
- Genshin Impact BasicsSkill
- Genshin CharactersSkill
- Cloud Gaming ChromeSkill
- Genshin CombatSkill
- Genshin EventsSkill
- Genshin Inventory and GearSkill
- Genshin Interaction SafetySkill
- Genshin Map and ExplorationSkill
- Genshin Navigation and InputSkill
- Genshin Progression and ResinSkill
- Genshin QuestsSkill
- Genshin Reward ClaimingSkill
- Genshin Shop and SpendingSkill
- Genshin SocialSkill
- Genshin UI ScreensSkill
- Welkin Moon Daily ClaimSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. 12 are common, 1 is distinctive, and 1 is very specific to this project.
12
Common
Most of the 157 edited versions we read keep these.
1
Distinctive
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 measured: kept by at least 6 in 10 of the 157 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.

