systematic-debugging SKILL.md skillA
systematic-debugging from jnpiyush/agentx is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add jnpiyush/agentx/systematic-debugging@git:20260915.f17c505Pins git:20260915.f17c505 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- jnpiyush/agentx
- Path
.github/skills/development/systematic-debugging/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260915.f17c505, committed Sep 15, 2026
- First version recorded
- May 17, 2026
- Size
- 7,261 bytes
- Repository stars
- 19
- License
- Apache-2.0
Disciplined debugging for stalled bug fixes. Use when an Engineer or Reviewer has tried two or more fixes that did not work, when symptoms keep moving, or when the same test keeps failing for different reasons. Forces root-cause investigation, pattern analysis, hypothesis testing, and a final implementation, in that order.
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 > WHEN: A bug fix has failed two or more times, the same test keeps failing for different reasons, or the symptom keeps moving when fixes are applied. Also use proactively for any `type:bug` that touches more than one file or crosses a module boundary. ## When to Use This Skill Load this skill when: - Two or more fixes for the same bug have not held - The failing test now fails in a different way after each attempt - A `type:bug` issue is non-trivial (more than a single-file typo) - A Reviewer has issued `CHANGES REQUESTED` twice on the same defect - You feel the urge to "try one more thing" instead of investigating Skip when: - The bug is a single-line obvious typo with no dependencies - The failure mode is fully understood and the fix is mechanical ## Prerequisites - Reproduction of the bug, or a failing test that captures it - Access to the relevant logs, stack traces, and recent commits - Time budget; this skill is slower than guess-and-fix, on purpose ## Rationalization Table The three-failed-fixes rule exists because LLMs and humans both reach for these instead of investigating. | Rationalization | Reality | |-----------------|---------| …
Read the whole file at its exact version.
How to install
mdr add jnpiyush/agentx/systematic-debugging@sha256:e2b8a8bf69f6ec20The line at the top of this page pins the label git:20260915.f17c505, 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_w4zhtfw7jbx7y5dm)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between May 17, 2026 and Sep 15, 2026, about one every 120 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260915.f17c505 latest | 2026-09-15 | f17c505 | 7,261 B | A | view · diff |
| git:20260517.4703a79 | 2026-05-17 | 4703a79 | 7,259 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 (7261 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
jnpiyush/agentx · 19 stars · license Apache-2.0 · pushed 2026-11-04 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_w4zhtfw7jbx7y5dm GET https://markdownregistry.com/api/v1/resolve?ref=jnpiyush/agentx/systematic-debugging GET https://markdownregistry.com/api/v1/blob/e2b8a8bf69f6ec2037916be054c5fb73f0dccfadb6a1490ba0fd1ab66859efc9
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.