Index of every page on this site: llms.txt
All skills
cursor avatar

/principle-fix-root-causes

@0b46ec3
by cursorcursor/plugins18k stars
1,933
Run it yourself

Apply when debugging. Trace each symptom back to the first place the system went wrong and fix it there. A guard is a fix only when the state it handles is legitimate.

Use this Skill: https://skilld.dev/gh/cursor/plugins/principle-fix-root-causes

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈49 tokens for metadata: the name and description. ≈201 when used: this file.

How this Skill uses context

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

This Skill turns off automatic use in Claude Code. Its description stays out of the automatic Skill list by default.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Fix Root Causes

Fix the fault, not the place where it surfaced. The root cause is the first place the system did something it should not do, or failed to handle a state it should handle.

  • Reproduce first. Ask "why" until the answer is a wrong decision in the code. When stuck, instrument and read the actual state.
  • Ask whether the state that triggered the symptom is legitimate. If it is, handle it where the code broke. If it should never exist, a check there hides the bug, so find what produced it. Guards, retries, swallowed errors, clamped values, and discarded state are the usual ways to hide a bug.
  • Fix the pattern, not the instance. Find every place with the same fault.
  • If the deciding fact took a deep dig, propose the cheap, always-on signal that would have shown it at first look.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2d3 checks · Risk SAFE
  • Gen Agent Trust Hub3d

    This skill provides text-based debugging principles and does not contain any code, network operations, or sensitive data access.

  • Socket2d

    No alerts

  • Snyk3d

    Risk: LOW · No issues

Signed by skilld at 0b46ec3. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 4 days ago
disable-model-invocation
true

README badge

README badge for cursor/plugins/principle-fix-root-causes