root-cause-investigation
Skill0 starsChanged 26 days agoMITView on GitHub
Investigate intermittent bugs, regressions, errors, or failing CI to isolate a defensible root cause before changing code. Diagnosis-only; use bug-fix-verification for remediation.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- sp1e/claude-skillstheir own version, first seen Oct 12, 2026
- chinthakat/agent-skillstheir own version, first seen Sep 21, 2026
- OneDro1d/onedroid-docstheir own version, first seen Sep 18, 2026
- chaakresh/claude-skillstheir own version, first seen Sep 7, 2026
- iiiburnyiii/agent-skillstheir own version, first seen May 14, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- sp1e/claude-skills★ 1same name
- chaakresh/claude-skills★ 0same name
- chinthakat/agent-skills★ 0same name
- iiiburnyiii/agent-skills★ 0same name
- OneDro1d/onedroid-docs★ 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
- acceptance-qaSkill
- architecture-reviewSkill
- bug-fix-verificationSkill
- dependency-upgradeSkill
- docs-syncSkill
- idea-to-scopeSkill
- implementation-planSkill
- independent-reviewSkill
- migration-safetySkill
- performance-investigationSkill
- pull-request-handoffSkill
- release-checkpointSkill
- security-reviewSkill
- surgical-changeSkill
- test-gap-auditSkill
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 3 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 8
Do not jump from the first error message to a patch.
- Distinctive: line 13
Run small, controlled experiments when the environment permits.
- Distinctive: line 14
Update hypotheses as evidence arrives.
“Common” is measured: kept by at least 6 in 10 of the 3 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
Root-cause investigation
Do not jump from the first error message to a patch. This skill investigates; it does not remediate.
- Establish symptoms with timestamps, affected versions, inputs, expected behavior, and the earliest reliable failure signal. Separate the user's report from observed evidence.
- Form no more than three competing explanations. State what observation would discriminate between them.
- Trace the relevant path: caller, state transitions, data shape, exceptions, retries, configuration, and recent changes. Search narrowly before searching everywhere.
- Run small, controlled experiments when the environment permits. Start with deterministic local reproductions; avoid writing to production or external systems. Record command, input, and outcome.
- Update hypotheses as evidence arrives. Do not label correlation as root cause. If no explanation survives testing, explicitly report a bounded unknown.
- Hand off the smallest candidate correction and a proposed regression check to
$bug-fix-verification. Do not edit the reviewed code during diagnosis.
Special cases
- CI-only failure: compare runtime versions, environment, time, ordering, data, and resource constraints rather than immediately retrying.
- Flaky test: check shared state, parallelism, nondeterministic order, leaked timers, and dependencies before increasing timeouts.
- Incident: treat secrets, live customer data, and deployment actions as separate authorization boundaries.
Output
Symptom, evidence timeline, hypotheses tested, most likely cause with confidence, reproduction, next safe action. Say clearly when the cause remains unconfirmed.
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.

