dantotsu
Skill7 starsChanged 16 days agoNo licenceView on GitHub
Use this skill when the user wants to investigate a bug, defect, incident, or quality issue and find its root cause — including requests to run a "5 whys" analysis, write a postmortem, do a root-cause analysis (RCA), figure out why a bug reached production or slipped past code review/QA, set up a recurring defect-analysis routine, or run a daily/weekly quality-improvement (Kaizen) triage. Also known as the Dantotsu method (Sadao Nomura's Toyota-derived defect-analysis approach, adapted for software). Trigger even if the user doesn't name the method explicitly — e.g. "why did this bug get through code review", "a client reported a bug, help me analyze it", "I want to understand why this keeps happening", "write up a root cause report for this defect", or "help me prioritize which fixes to actually ship this week".
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
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 308,232 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.
In this repository53 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- documentationSkill
- fastify-best-practicesSkill
- git-heroSkill
- handoffSkill
- initSkill
- linting-neostandard-eslint9Skill
- nodejs-coreSkill
- nodeSkill
- oauthSkill
- octocatSkill
- simpleSkill
- skill-optimizerSkill
- snipgrapherSkill
- typescript-magicianSkill
- typescriptSkill
- c4-diagramSkill
- c-cppSkill
- clean-codeSkill
- code-ownershipSkill
- communicationSkill
- data-systemsSkill
- elixirSkill
- elmSkill
- example-mappingSkill
- explain-codeSkill
- fetch-pr-corpusSkill
- git-heroSkill
- golangSkill
- javaSkill
- kanoSkill
- lean-senseiSkill
- lisperSkill
- logging-daily-progressSkill
- markdownSkill
- mikado-methodSkill
- object-oriented-programmingSkill
- ocamlSkill
- phpSkill
- pythonSkill
- repo-docsSkill
- rescriptSkill
- rest-api-designSkill
- reviewSkill
- rubySkill
- rustSkill
- show-me-the-codeSkill
- smalltalk-pharoSkill
- testingSkill
- the-architectSkill
- typescriptSkill
- vendor-referenceSkill
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.