diagnosing-bugs is agent-read markdown (skill) from kunolu/640-skills: Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Diagnosing Bugs
A discipline for hard bugs. Skip phases only when explicitly justified.
When exploring the codebase, read `CONTEXT.md` (if it exists) to get a clear mental model of the relevant modules, and check ADRs in the area you're touching.
## Redact
This skill has you show commands, outputs and captured artifacts. **Redact every secret first**: write `<REDACTED>` in its place. Build loops against env vars, so the credential stays in the environment rather than in what you show. Captured artifacts carry auth headers: quote only the lines that carry the signal.
If the redacted output is not enough to diagnose the bug, say so and ask the user.
## Phase 1: Build a feedback loop
**This is the skill.** Everything else is mechanical. If you have a **tight** pass/fail signal for the bug (one that goes red on _this_ bug), you will find the cause; bisection, hypothesis-testing, and instrumentation all just consume it. If you don't have one, no amount of staring at code will save you.
Spend disproportionate effort here. **Be aggressive. Be creative. Refuse to give up.**
### Ways to construct one, in roughly this order
…
Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
GET https://markdownregistry.com/api/v1/artifacts/art_s6d4anwl3iqhnh7m
GET https://markdownregistry.com/api/v1/resolve?ref=kunolu/640-skills/diagnosing-bugs
GET https://markdownregistry.com/api/v1/blob/77f3cf31bc99b2f49af943222526531fcc9fc41d047626d3640e875e85af3e84
Your agent 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.
kunolu/640-skills · sbtd-workflow-onboard/assets/external-skills/stable/skills/codebase-design/SKILL.md · Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find…
kunolu/640-skills · sbtd-workflow-onboard/assets/external-skills/stable/skills/domain-modeling/SKILL.md · Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a CONTEXT.md…
kunolu/640-skills · sbtd-workflow-onboard/assets/external-skills/stable/skills/grill-with-docs/SKILL.md · A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
kunolu/640-skills · sbtd-workflow-onboard/assets/external-skills/stable/skills/grilling/SKILL.md · Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or…
kunolu/640-skills · sbtd-workflow-onboard/assets/external-skills/stable/skills/handoff/SKILL.md · Compact the current conversation into a handoff document for another agent to pick up.
kunolu/640-skills · sbtd-workflow-onboard/assets/external-skills/stable/skills/i-have-adhd/SKILL.md · Shape output for a reader with ADHD: lead with the next action, number multi-step work, restate state across turns…
kunolu/640-skills · sbtd-workflow-onboard/assets/external-skills/stable/skills/impeccable/SKILL.md · Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt…
kunolu/640-skills · sbtd-workflow-onboard/assets/external-skills/stable/skills/ponytail-audit/SKILL.md · Whole-repo audit for over-engineering. Like ponytail-review, but scans the entire codebase instead of a diff: a ranked…
kunolu/640-skills · sbtd-workflow-onboard/assets/external-skills/stable/skills/ponytail-debt/SKILL.md · Harvest every `ponytail:` comment in the codebase into a debt ledger, so the deliberate shortcuts and deferrals…
kunolu/640-skills · sbtd-workflow-onboard/assets/external-skills/stable/skills/ponytail-review/SKILL.md · Code review focused exclusively on over-engineering. Finds what to delete: reinvented standard library, unneeded…
mxyhi/ok-skills · diagnosing-bugs/SKILL.md · Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports…
asymmetric-al/core · .agents/skills/diagnosing-bugs/SKILL.md · Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports…
miosa-osa/osa · priv/skills/diagnosing-bugs/SKILL.md · Diagnose broken, failing, incorrect, flaky, or unexpectedly slow software. Use whenever a user reports a bug…
gtapps/claude-code-hermit · plugins/claude-code-dev-hermit/skills/diagnosing-bugs/SKILL.md · Diagnosis loop for hard bugs and performance regressions. Builds a red-capable feedback loop and runs it before…
akillness/jeo-skills · .agent-skills/diagnosing-bugs/SKILL.md · Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports…
vodailocz/kilo-kit-mcp · skills/engineering/diagnosing-bugs/SKILL.md · Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports…
j-star-films-studios/vibecode-protocol-suite · assets/.agent/skills/code-intelligence/diagnosing-bugs/SKILL.md · Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports…
rudycity/superagent · .agents/skills/diagnosing-bugs/SKILL.md · Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports…