systematic-debugging SKILL.md skillA
systematic-debugging from kbwen/agentic-os is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add kbwen/agentic-os/systematic-debugging@git:20260910.7c13f5dPins git:20260910.7c13f5d in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- kbwen/agentic-os
- Path
.agents/skills/systematic-debugging/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260910.7c13f5d, committed Sep 10, 2026
- First version recorded
- Apr 12, 2026
- Size
- 1,985 bytes
- Repository stars
- 237
- License
- MIT
Use when investigating a bug, test failure, flaky test, unexpected behavior, or a hotfix, or an unexplained or failed fix; find the root cause first.
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 ## Overview The core of systematic debugging is: **understand first, then fix**. When encountering a bug, clarify symptoms, reproduction conditions, and blast radius. Draw hypotheses, verify them with experiments to isolate the root cause, and only then submit a minimal, verifiable fix. ## Ironclad Rules 1. **No random patching**: Do not submit fixes without root cause evidence. 2. **Change one variable at a time**: Prevent unexplainable results from touching multiple areas at once. 3. **Fixes MUST include evidence**: Include reproduction steps, verification, and regression results. ## When to Use - Hotfix incident response. - Flaky tests. - Cross-module anomalies that aren't intuitively obvious. - Any "fixed but I don't know why" risk scenarios. ## Four-Phase Process ### Phase 1: Observe - Precisely record error messages, timestamps, and input conditions. - Create a Minimal Reproducible Example (MRE). - Mark the blast radius (affected modules/users). ### Phase 2: Hypothesize - Propose 1–3 testable root cause hypotheses. - Design "falsifiable" checks for each hypothesis. - Prioritize high-probability, low-cost verifiable items. …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_kd47rx7d4suqq3ax/9bee4d30a78701f4fe8149cfe22cbd2d82116af0757c1e777629f51ada488442.json
Then /plugin install systematic-debugging@markdownregistry-kd47rx7d4suqq3ax in Claude Code. It installs git:20260910.7c13f5d, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add kbwen/agentic-os/systematic-debugging@sha256:9bee4d30a78701f4The line at the top of this page pins the label git:20260910.7c13f5d, 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_kd47rx7d4suqq3ax)
2 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in kbwen/agentic-os/systematic-debugging since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of systematic-debugging from somewhere else? Ask it: where did my systematic-debugging come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 2 versions of this file, between Apr 12, 2026 and Sep 10, 2026, about one every 151 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260910.7c13f5d latest | 2026-09-10 | 7c13f5d | 1,985 B | A | view · diff |
| git:20260412.c1ced66 | 2026-04-12 | c1ced66 | 1,930 B | A | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/systematic-debugging/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
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 (1985 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
kbwen/agentic-os · 237 stars · license MIT · pushed 2026-11-13 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_kd47rx7d4suqq3ax GET https://markdownregistry.com/api/v1/resolve?ref=kbwen/agentic-os/systematic-debugging GET https://markdownregistry.com/api/v1/blob/9bee4d30a78701f4fe8149cfe22cbd2d82116af0757c1e777629f51ada488442
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 kbwen/agentic-os
Every file in kbwen/agentic-os
Other files named systematic-debugging
Browse by kind, by grade A, or by owner.
Kept in .agents/skills, the folder Codex reads. More agent skills for Codex.