diagnosing-bugs SKILL.md skillA
diagnosing-bugs from ehnruiz/claude-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add ehnruiz/claude-skills/diagnosing-bugs@git:20261020.b184c85Pins git:20261020.b184c85 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- ehnruiz/claude-skills
- Path
skills/diagnosing-bugs/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261020.b184c85, committed Oct 20, 2026
- First version recorded
- Oct 15, 2026
- Size
- 5,423 bytes
- Repository stars
- 3
- License
- MIT
A disciplined loop for hard bugs, flaky tests and performance regressions - build a red-capable feedback loop first, reproduce and minimize, rank falsifiable hypotheses, instrument one variable at a time, then repair and remove the probes. Use when the user says "diagnose", "debug this" or "why is this failing", reports a wrong result, a crash, a timeout, a flaky test or a slowdown, or when a first-glance fix did not hold.
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
# Diagnosing bugs A discipline for hard bugs. Skip a phase only when you can say why. Credit and license: `LICENSE.md` in this folder. **Project copy first.** If the repository has its own `.claude/skills/diagnosing-bugs/SKILL.md`, read it and follow it instead of this file. A skill installed for all your projects outranks a project skill with the same name, so without this step a repository's own version of this skill would never run. Before exploring, read the project's architecture and known-limitations docs if it has them; some "bugs" are documented gaps. ## Redact You will show commands, outputs and captured artifacts. **Redact every secret first**: write `<REDACTED>` in its place. Build loops against environment variables so tokens, webhook URLs and cookies stay in the environment, not in what you show. Quote only the lines that carry the signal. ## Phase 1: Build a feedback loop **This is the skill.** With a tight pass/fail signal that goes red on *this* bug, you will find the cause; bisection, hypotheses and instrumentation all just consume it. Without one, no amount of reading code will save you. Spend disproportionate effort here. …
Read the whole file at its exact version.
How to install
mdr add ehnruiz/claude-skills/diagnosing-bugs@sha256:8f008cbf9a422944The line at the top of this page pins the label git:20261020.b184c85, 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_emafqhutp2dcjxna)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Oct 15, 2026 and Oct 20, 2026, about one every 2 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261020.b184c85 latest | 2026-10-20 | b184c85 | 5,423 B | A | view · diff |
| git:20261015.dd12a4b | 2026-10-15 | dd12a4b | 5,198 B | A | view · diff |
| git:20261015.0b3e11b | 2026-10-15 | 0b3e11b | 5,203 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 (5423 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
ehnruiz/claude-skills · 3 stars · license MIT · pushed 2026-10-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_emafqhutp2dcjxna GET https://markdownregistry.com/api/v1/resolve?ref=ehnruiz/claude-skills/diagnosing-bugs GET https://markdownregistry.com/api/v1/blob/8f008cbf9a4229449051545219efd36ad4d026a2a3629ad1e2d9320b8c4b5513
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 ehnruiz/claude-skills
Every file in ehnruiz/claude-skills