systematic-debugging SKILL.md skillA
systematic-debugging from lawzava/megapowers is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add lawzava/megapowers/systematic-debugging@git:20261101.662c2d5Pins git:20261101.662c2d5 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- lawzava/megapowers
- Path
plugins/megapowers/skills/systematic-debugging/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261101.662c2d5, committed Nov 1, 2026
- First version recorded
- Oct 11, 2026
- Size
- 3,345 bytes
- Repository stars
- 8
- License
- MIT
Use when a bug, failing or flaky test, production incident, unexpected output, or performance regression has an unknown cause.
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 Find the root cause before attempting a fix. Read the complete failure. When many checks fail, list them and group by likely shared cause before fixing the first. Reproduce it with a fast, deterministic loop that goes red on the reported symptom, then minimize it. Trace the bad value or condition backward across boundaries, compare it with a working path, and inspect recent changes without assuming they are causal. When a hosted service or CI provider fails, check its status page first. For flakiness, identify nondeterministic input, timing, shared state, or resource contention instead of retrying until green. For slowness, use [performance measurement](references/performance.md). If output is filtered or truncated, retrieve the relevant raw diagnostics before diagnosing the failure. If raw evidence remains unavailable or incomplete, treat the diagnosis as inconclusive. Redact sensitive values before quoting captured output. Do not repeat a side effect solely to recover output. Before choosing the fix location, inspect callers of the implicated code and identify whether they depend on a shared invariant. Add regression coverage for …
Read the whole file at its exact version.
How to install
mdr add lawzava/megapowers/systematic-debugging@sha256:0fe0af7904ec44f5The line at the top of this page pins the label git:20261101.662c2d5, 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_mgwv5yxt4gymnkcf)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Oct 11, 2026 and Nov 1, 2026, about one every 7 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261101.662c2d5 latest | 2026-11-01 | 662c2d5 | 3,345 B | A | view · diff |
| git:20261021.ffb3826 | 2026-10-21 | ffb3826 | 3,336 B | A | view · diff |
| git:20261011.3772703 | 2026-10-11 | 3772703 | 3,090 B | A | view · diff |
| git:20261011.b2d53fa | 2026-10-11 | b2d53fa | 2,999 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 (3345 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
lawzava/megapowers · 8 stars · license MIT · pushed 2026-11-02 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_mgwv5yxt4gymnkcf GET https://markdownregistry.com/api/v1/resolve?ref=lawzava/megapowers/systematic-debugging GET https://markdownregistry.com/api/v1/blob/0fe0af7904ec44f5c2757ad8b5f008c6856eb6fe2a53c4d5aa404d72989ab5b1
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 lawzava/megapowers
Every file in lawzava/megapowers