systematic-debugging SKILL.md skillA
systematic-debugging from frnkgns/gentjinskills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add frnkgns/gentjinskills/systematic-debugging@git:20261007.d578084Pins git:20261007.d578084 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- frnkgns/gentjinskills
- Path
skills/systematic-debugging/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261007.d578084, committed Oct 7, 2026
- First version recorded
- Sep 26, 2026
- Size
- 8,524 bytes
- Repository stars
- 7
- License
- none declared
Find the root cause of a defect with a disciplined loop-to-evidence-to-hypothesis-to-fix workflow. Use when something is broken, behavior is unexpected, a build or test suddenly fails, a regression is reported, data reaches the wrong process/session/component, the user asks "why is this happening?", a symptom appears only intermittently, or several attempted fixes have already failed.
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 ## Rule Evidence before edits. Do not start with random code changes, and do not repeatedly patch symptoms. ## Phase 1 — Build a feedback loop This phase is the skill. Everything after it consumes its output. Without a loop that goes red on this specific defect, bisection, hypothesis testing, and instrumentation are all guesswork dressed as method. Construct the loop, roughly in this order: 1. A failing test at whatever seam reaches the defect. 2. A curl or HTTP script against a running dev server. 3. A CLI invocation with a fixed input, diffed against known-good output. 4. A headless browser script that drives the UI and asserts on the DOM, console, or network. 5. A replayed captured artifact: a real request, payload, or event log saved to disk and run through the path in isolation. 6. A throwaway harness exercising a minimal subset with one entry point. 7. A property or fuzz loop when the symptom is intermittent and wrong, running many inputs to expose the failure mode. 8. A bisection harness when the defect appeared between two known states. Then tighten it. A loop is a product, not a means: …
Read the whole file at its exact version.
How to install
mdr add frnkgns/gentjinskills/systematic-debugging@sha256:4b80d48efcc3bd53The line at the top of this page pins the label git:20261007.d578084, 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_sssl6lzpp23l25zh)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Sep 26, 2026 and Oct 7, 2026, about one every 11 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261007.d578084 latest | 2026-10-07 | d578084 | 8,524 B | A | view · diff |
| git:20260926.3185b84 | 2026-09-26 | 3185b84 | 2,280 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 (8524 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
frnkgns/gentjinskills · 7 stars · license none declared · pushed 2026-10-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_sssl6lzpp23l25zh GET https://markdownregistry.com/api/v1/resolve?ref=frnkgns/gentjinskills/systematic-debugging GET https://markdownregistry.com/api/v1/blob/4b80d48efcc3bd53595d5ba19d8712bcc0faf59ae1a1413344017e7f4fa39cfd
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 frnkgns/gentjinskills
Every file in frnkgns/gentjinskills