Skip to content
Back to skills

Principle Fix Root Causes

ASecurity

Use for root-cause repair only on explicit request. Requires fixing causes instead of symptoms.

  • 11 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added September 2, 2026
ai-agentsdebugging

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned September 24, 2026

npx -y skills add bostonaholic/team --skill principle-fix-root-causes --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Principle Fix Root Causes?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Principle Fix Root Causes
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/bostonaholic-principle-fix-root-causes/badge)](https://www.skillsdirectory.com/skills/bostonaholic-principle-fix-root-causes)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: principle-fix-root-causes
description: 'Use for root-cause repair only on explicit request. Requires fixing causes instead of symptoms.'
disable-model-invocation: true
---

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

Files in this skill

  • SKILL.md1.7 KB
  • agents/openai.yaml230 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.