principle-fix-root-causes

Guides debugging by tracing symptoms to root causes instead of applying symptom-level workarounds.

Updated Jul 29, 2026
One-click install
npx skills add https://github.com/mmdmcy/fluttAIrbar --skill principle-fix-root-causes-mmdmcy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: principle-fix-root-causes
Source: https://github.com/mmdmcy/fluttAIrbar/tree/main/plugins/pstack/skills/principle-fix-root-causes
Command: npx skills add https://github.com/mmdmcy/fluttAIrbar --skill principle-fix-root-causes-mmdmcy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Debugging often produces quick patches that silence symptoms while the real bug survives, accumulating fragile workarounds that make the codebase harder to reason about. This Skill enforces a disciplined root-cause debugging methodology so fixes address the actual defect. ## Core Features & Use Cases - Root-Cause Tracing: Reproduce the bug first, then ask "why" repeatedly until the true cause is found, rather than guessing. - Anti-Pattern Detection: Resist nil-check guards that silence crashes, flag workarounds needing paragraph-long justifying comments, and grep for repeated instances of the same defective pattern. - Restart-Bug Heuristic: When something fails after restart, suspect stale persistent state (config files, caches, lock files, serialized state) before suspecting code, since code does not change between runs. - Use Case: A crash reappears after every app restart. Instead of adding another defensive check, the Skill directs you to inspect persisted state files, confirm that clearing one restores behavior, and implement state validation as the real fix. ## Quick Start Ask the AI to debug a recurring bug using the principle-fix-root-causes workflow, reproducing it first and tracing it to its root cause before writing any fix.

Frequently Asked Questions about principle-fix-root-causes

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find the root cause of a bug instead of patching symptoms?▼

Reproduce the bug first, since an unreproducible bug cannot have a verified fix. Then ask "why" repeatedly until you reach the root cause, and fix it there rather than adding guards that only silence the visible symptom.

Why is adding a nil check to stop a crash considered a bad fix?▼

A nil check that silences a crash is a symptom fix: it hides the defect while the underlying cause remains. Symptom fixes accumulate, making the system harder to reason about and increasing total debugging time.

Why does a bug only happen after restarting the application?▼

Code does not change between runs, but state does. Restart-dependent failures usually come from stale persistent state such as config files, caches, lock files, or serialized state, so suspect and validate those first.

What should I do when I am stuck and cannot find a bug's cause?▼

Instrument the code instead of guessing. Add logging and read the actual error output so your diagnosis is based on observed behavior rather than assumptions.

When is a workaround acceptable instead of a root-cause fix?▼

If a workaround needs a paragraph-long comment to justify it, the code itself is wrong and should be fixed. Also grep for the same defective pattern elsewhere and fix all instances, not just the one that surfaced.