mcpField
P
principle-fix-root-causes

principle-fix-root-causes

github.com/cursorDevelopment14.6k5.2k installsUpdated 1d ago
Repository

About principle-fix-root-causes

Fix Root Causes is a debugging principle for locating and correcting the fault that produced a symptom, rather than patching where it appeared. It gives a practical investigation pattern and cautions against workarounds that conceal invalid state or repeated defects.

Key features

  1. 01Reproduce failures before changing code
  2. 02Trace causes back to faulty decisions
  3. 03Inspect actual errors and state
  4. 04Distinguish valid from invalid states
  5. 05Search for repeated fault patterns
  6. 06Improve signals when diagnosis is difficult

Use cases

  1. 01Diagnosing a bug that surfaces downstream
  2. 02Investigating failures after a restart
  3. 03Replacing guards or retries that mask defects

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/cursor/plugins --skill principle-fix-root-causes

After installing, type/principle-fix-root-causesin Claude Code to confirm it loaded.

Details

From the project README

Fix Root Causes

When debugging, fix the fault, not the place where it surfaced. The symptom is where a wrong state became visible. The root cause is the first place the system did something it should not do, or failed to handle a state it should handle.

Why: A symptom fix hides the evidence and leaves the fault free to surface somewhere else. Each one makes the system harder to reason about, because the code now carries a workaround for a bug that nobody named.

Pattern:

  • Reproduce first.
  • Ask "why" at each step until the answer is a wrong decision in the code, not a consequence of an earlier one.
  • When stuck, instrument. Read the actual error and the actual state. Do not guess.
  • Ask whether the state that triggered the symptom is legitimate. If the system may be in that state, the code that broke on it is the root cause, and handling the state there is the fix. If the state should never exist, a check where it broke hides the bug. Find what produced the state. Guards, retries, swallowed errors, clamped values, and discarded state are the usual ways to hide a bug.
  • When something fails only after a restart, suspect persisted state first: config files, caches, lock files, serialized state.
  • Check for the pattern, not just the instance. Find every place with the same fault and fix them all.
  • If a workaround needs a paragraph-long comment to justify it, the code is wrong. Fix the code, not the comment.
  • If the deciding fact took a deep dig to find, propose the cheap, always-on signal that would have shown it at first look.

Comments

Markdown supported