systematic-debugging SKILL.md skillA
systematic-debugging from brunob54/superpowers-orchestrator is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add brunob54/superpowers-orchestrator/systematic-debugging@git:20261021.eca14f1Pins git:20261021.eca14f1 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- brunob54/superpowers-orchestrator
- Path
skills/systematic-debugging/SKILL.md- Versions recorded
- 7
- Latest version
- git:20261021.eca14f1, committed Oct 21, 2026
- First version recorded
- Mar 23, 2026
- Size
- 7,357 bytes
- Repository stars
- 3
- License
- MIT
Invoke BEFORE attempting any fix when a bug, test failure, error, warning, unexpected behavior, or performance regression appears. Enforces hypothesis-driven root cause analysis — no fix without evidence. Triggers on: error messages, stack traces, "it's broken", "not working", "bug", test failures, blank/white screens, "works locally but not in production", performance degradation, console warnings, "can't figure out why". Also routed by using-superpowers for debugging tasks.
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
# Systematic Debugging Do root-cause investigation before proposing fixes. ## Iron Law **No fix without evidence for root cause.** This is non-negotiable. Every fix must trace back to a proven root cause. A fix applied without understanding why it works is not a fix — it is a mask. ## Four Phases ### Phase 0: Check Known Issues - If `known-issues.md` exists at the project root, search it for the error message, error code, or failing test name. - If a match is found, try the documented solution **first**. If it resolves the issue, stop — no further investigation needed. - If no match or the documented solution doesn't work, proceed to Phase 1. ### Phase 1: Investigate - Read the **full** error output — not just the last line. - Reproduce the bug reliably. If you cannot reproduce, you cannot fix. For tests that fail only in certain orderings (test pollution), run `find-polluter.sh` from this skill's directory to identify which test is corrupting shared state. - Check recent changes — what changed since it last worked? - If `context-snapshot.json` exists at the project root: run `git rev-parse HEAD` and compare to `git_hash` in the file. …
Read the whole file at its exact version.
How to install
mdr add brunob54/superpowers-orchestrator/systematic-debugging@sha256:10807dd6e27bd3e3The line at the top of this page pins the label git:20261021.eca14f1, 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.
[](https://markdownregistry.com/a/art_pnqgkptjpwnllyxy)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 7 versions of this file, between Mar 23, 2026 and Oct 21, 2026, about one every 35 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261021.eca14f1 latest | 2026-10-21 | eca14f1 | 7,357 B | A | view · diff |
| git:20261005.18a4467 | 2026-10-05 | 18a4467 | 7,301 B | A | view · diff |
| git:20260415.0a78a70 | 2026-04-15 | 0a78a70 | 7,105 B | A | view · diff |
| git:20260329.4a8e1f5 | 2026-03-29 | 4a8e1f5 | 6,823 B | A | view · diff |
| git:20260328.4349b30 | 2026-03-28 | 4349b30 | 5,676 B | A | view · diff |
| git:20260325.1b3a95f | 2026-03-25 | 1b3a95f | 5,510 B | A | view · diff |
| git:20260323.9636c5c | 2026-03-23 | 9636c5c | 5,348 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (7357 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
brunob54/superpowers-orchestrator · 3 stars · license MIT · pushed 2026-11-02 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_pnqgkptjpwnllyxy GET https://markdownregistry.com/api/v1/resolve?ref=brunob54/superpowers-orchestrator/systematic-debugging GET https://markdownregistry.com/api/v1/blob/10807dd6e27bd3e321bda6d33a68b88de617fae87a01230352258eb4e52d9b96
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.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from brunob54/superpowers-orchestrator
Every file in brunob54/superpowers-orchestrator