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.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# 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.
The line at the top of this page pins the label git:20261013.9e6954c, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (1246 bytes)
pass: No zero-width or bidi control characters
pass: No instruction hidden inside an HTML comment
pass: No link to an exfiltration or paste host
pass: No credential-shaped string
pass: No instruction to send local credentials anywhere
pass: No text hidden with inline styles
pass: No prompt-injection phrasing
pass: No curl or wget piped into a shell
pass: No recursive delete of root, home or parent
pass: No instruction to read or print local credentials
pass: No base64 blob over 200 characters
pass: No link to a raw IP address
pass: No script tag
Source
GitHub
nightly-labs/openbot · 5,267 stars · license a license file GitHub does not identify · pushed 2026-11-04 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_itscfuq74bsnvezw
GET https://markdownregistry.com/api/v1/resolve?ref=nightly-labs/openbot/principle-fix-root-causes
GET https://markdownregistry.com/api/v1/blob/ba4cd38da1dcc8fe5432feb64457cba95594736a9b21b2ebf8f8c52aee068707
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
nightly-labs/openbot · .agents/skills/babysit/SKILL.md · Babysit a pull request through the NorbiAI review loop until no valid issue remains. Fix valid findings, rebut false…
nightly-labs/openbot · .agents/skills/biome-anti-slop/SKILL.md · Install and configure vendored Biome anti-slop GritQL rules in a local TypeScript or JavaScript repository. Use when a…
nightly-labs/openbot · .agents/skills/prototype/SKILL.md · Build several different design directions (3 by default) for a feature or issue as Storybook stories, show them to the…
nightly-labs/openbot · .agents/skills/release-upgrade-safety/SKILL.md · Audit a pending OpenBot release for upgrade and data-loss hazards before the version is bumped or tagged. Use when…
nightly-labs/openbot · .agents/skills/ship/SKILL.md · Ship the current branch to main. Review the diff, fix findings, open the pull request, babysit the NorbiAI review and…
nightly-labs/openbot · .agents/skills/signal-deploy/SKILL.md · Check and deploy Signal (the `remote-api` service in `remote/`) to production from a release tag. Use when asked to…
nightly-labs/openbot · .agents/skills/smoke-and-ship/SKILL.md · Smoke test the current branch, then ship it to main only when all smoke items pass. Use when the user asks to smoke and…
nightly-labs/openbot · .agents/skills/smoke/SKILL.md · Start one or more local OpenBot dev instances and smoke test the features that the current changes or a pull request…
nightly-labs/openbot · .agents/skills/triage/SKILL.md · Triage one GitHub issue or bug report. Decide if it is valid, find the root cause, and fix it. Push back with evidence…
nightly-labs/openbot · .agents/skills/zaidan/SKILL.md · Install and configure the Zaidan component registry in an existing SolidJS codebase, and recommend Zaidan components…
cursor/plugins · pstack/skills/principle-fix-root-causes/SKILL.md · Apply when debugging. Trace each symptom back to the first place the system went wrong and fix it there. A guard is a…
cursor/plugins · harness/pstack/claude-code/skills/principle-fix-root-causes/SKILL.md · Apply when debugging. Trace each symptom back to the first place the system went wrong and fix it there. A guard is a…
michael-denyer/pstack-claude · plugins/pstack/skills/principle-fix-root-causes/SKILL.md · Apply when debugging. Trace each symptom back to the first place the system went wrong and fix it there. A guard is a…
backnotprop/pstack · skills/principle-fix-root-causes/SKILL.md · Apply when debugging. Trace each symptom back to the first place the system went wrong and fix it there. A guard is a…
iap/pstack-hermes · skills/principle-fix-root-causes/SKILL.md · Apply when debugging. Trace each symptom to its root cause and fix it there; reproduce first, ask why until you reach…
j-star-films-studios/vibecode-protocol-suite · assets/.agent/skills/engineering-principles/fix-root-causes/SKILL.md · Apply when debugging. Trace each symptom to its root cause and fix it there; reproduce first, ask why until you reach…
barbieri/local-openfinance · .agents/skills/principle-fix-root-causes/SKILL.md · Apply when debugging. Trace each symptom to its root cause and fix it there; reproduce first, ask why until you reach…
theonlyfusioncube/potetos-for-everyone · skills/principle-fix-root-causes/SKILL.md · Reproduce the symptom, trace causality until one mechanism explains it, and fix that mechanism rather than compensating…
