Principle Fix Root Causes

by cursorccb5507cec15No license10K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated today

Apply when debugging. Trace each symptom to its root cause and fix it there; reproduce first, ask why until you reach it, resist nil-check guards that silence crashes.

Instructions onlySoftware Development
AI-generated overview

Debugging guidance that traces symptoms to root causes instead of applying workaround fixes.

What it does
This skill provides a debugging principle set: reproduce the problem first, ask why until the root cause is reached, and fix the code there rather than adding guards. It advises against nil-check guards that silence crashes, against workarounds needing long justifying comments, and recommends searching for the same pattern in other places and instrumenting rather than guessing. It also notes that failures after restart should first be suspected as stale persistent state such as config files, caches, lock files, or serialized state.
When to use it
Use it when debugging a defect and deciding where the fix belongs. It fits situations where a crash was silenced with a guard, where a workaround keeps accumulating, or where something fails after a restart.
Requirements
No tools, packages, or credentials; it is instructions only and ships no scripts.

Fix Root Causes

When debugging, do not fix symptoms. Trace every problem to its root cause and fix it there.

Why: Symptom fixes accumulate. Each workaround makes the system harder to reason about, and the real bug remains. Root-cause fixes are slower upfront but reduce total debugging time.

Pattern:

  • Reproduce first
  • Ask "why" until you hit the root cause
  • Do not add guards (adding a nil check to silence a crash is a symptom fix)
  • If a workaround needs a paragraph-long comment to justify it, the code is wrong (fix the code, not the comment)
  • Check for the pattern, not just the instance (grep for the same pattern, fix all instances)
  • When stuck, instrument. Don't guess (add logging, read the actual error)

Restart bugs: suspect state before code

When something "fails after restart," suspect stale persistent state first: config files, caches, lock files, serialized state. If clearing a state file restores behavior, prioritize state validation as the fix.

Source and attribution

Source:cursor/pluginsinpstack/skills/principle-fix-root-causesat commitccb5507

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal