debugging SKILL.md skillA
debugging from prabhdeepsingh/claude-plugins is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add prabhdeepsingh/claude-plugins/debugging@git:20260913.4e5ade4Pins git:20260913.4e5ade4 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- prabhdeepsingh/claude-plugins
- Path
sonu/skills/debugging/SKILL.md- Versions recorded
- 6
- Latest version
- git:20260913.4e5ade4, committed Sep 13, 2026
- First version recorded
- Jul 29, 2026
- Size
- 16,225 bytes
- Repository stars
- 4
- License
- MIT
The scientific debugging loop — reproduce first, pull the real event from the repo's observability stack, one hypothesis → one change → one observation, revert failed attempts, escalate instead of thrash. INVOKE PROACTIVELY when diagnosing any bug, error, stack trace, failing or flaky test, crash, regression, or production incident — even a bare pasted error. Not for building features ([[tdd]] + [[code-standards]]); this governs finding WHY it's broken.
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
# Debugging — hypothesis testing, not patch roulette Debugging is a science experiment, not a repair job. You form a theory of what's wrong, make the *one* change that theory predicts will alter the outcome, and observe. Most debugging time is wasted by skipping that discipline: patching where the error *appeared* instead of where it *originated*, changing three things at once, or trying fixes in a loop and keeping the wreckage of the ones that failed. The rules below are the difference between an hour and a day — and between a fix and a fix-shaped bug. ## How to apply this Run the loop in order: reproduce (for a production report, pull the real event first — section 2 feeds section 1) → read → locate → hypothesize → test the hypothesis → fix → prove. Don't skip ahead to "fix" — a fix you can't connect to a confirmed cause is a guess with good posture. **And stop the line.** When something unexpected breaks mid-task, this loop preempts the feature work — don't push past a failing test or broken build to keep building. Errors compound: an unfixed bug in step 3 makes steps 4–6 wrong, and the wreckage multiplies the diagnosis. …
Read the whole file at its exact version.
How to install
mdr add prabhdeepsingh/claude-plugins/debugging@sha256:c58a2990a4a487aaThe line at the top of this page pins the label git:20260913.4e5ade4, 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_qav6636jupbyzftl)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 6 versions of this file, between Jul 29, 2026 and Sep 13, 2026, about one every 9 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260913.4e5ade4 latest | 2026-09-13 | 4e5ade4 | 16,225 B | A | view · diff |
| git:20260906.c8d9cf2 | 2026-09-06 | c8d9cf2 | 13,154 B | A | view · diff |
| git:20260827.d52dc18 | 2026-08-27 | d52dc18 | 12,334 B | A | view · diff |
| git:20260826.3bb29a7 | 2026-08-26 | 3bb29a7 | 12,035 B | A | view · diff |
| git:20260825.06c64c5 | 2026-08-25 | 06c64c5 | 10,610 B | A | view · diff |
| git:20260729.94bdcd7 | 2026-07-29 | 94bdcd7 | 10,297 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 (16225 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
prabhdeepsingh/claude-plugins · 4 stars · license MIT · pushed 2026-09-13 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_qav6636jupbyzftl GET https://markdownregistry.com/api/v1/resolve?ref=prabhdeepsingh/claude-plugins/debugging GET https://markdownregistry.com/api/v1/blob/c58a2990a4a487aa2c41bbf787db70247418fce5d44173c3a4e66d3ed6153fcc
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 prabhdeepsingh/claude-plugins
Every file in prabhdeepsingh/claude-plugins