agentleFS
future-minefuture-mine/claude-skill/skills/root-cause-investigator/SKILL.md

root-cause-investigator

Skill1 starsChanged 36 days agoNo licenceView on GitHub

Find and PROVE the true root cause of a production bug or manual-test failure in a legacy system — without proposing a fix until the cause is proven. Use this whenever something is wrong in a live/production/legacy system and the real cause isn't obvious: triggers on "there's a bug in production", "this fails in the live app", "manual testing turned up a failure", "users are seeing X but I don't know why", "intermittent error in prod", or "I need to find the real cause before touching anything". It follows a strict order — reliably reproduce → instrument and observe the actual data flow → trace the causal chain backward to separate symptom from true cause → prove the cause by toggling it → write a concise root-cause record — then HALTS for human confirmation of the diagnosis. It diagnoses only; surgical-fixer applies the fix. Prefer this over the greenfield debugger whenever the system is in production / legacy and understanding the cause matters more than a quick patch.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    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 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.

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.