diagnose-bug skillA
diagnose-bug is agent-read markdown (skill) from flurdy/agent-skills: Evidence-led, read-only bug diagnosis using minimal reproduction, boundary isolation, ranked hypotheses, and explicit falsification tests before any fix is proposed..
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
# Diagnose Bug Find what causes an observed failure before proposing implementation. Work from evidence: ```text reproduce → isolate → hypothesize → falsify → conclude ``` Diagnosis is read-only. It may run safe tests and inspect code, logs, configuration shape, and tracker context, but it does not edit code, tests, configuration, or trackers. ## When to use Use `/diagnose-bug` when: - the symptom is reproducible but the cause is unknown; - a regression crosses modules, services, environments, or asynchronous boundaries; - the failure is intermittent, input-specific, timing-sensitive, or production-only; - several plausible explanations exist and speculative fixes would be risky; - the user asks for root-cause analysis, investigation, isolation, or diagnosis. Usually skip it when: - a deterministic failing test and direct source trace already establish the cause; - the root cause is known and the request is purely to implement the fix; - the work is a feature, refactor, architecture plan, or post-fix verification; - the only question is whether an existing implementation satisfies requirements—use `/verify-task` instead. ## Usage ```text …
Read the whole file at its exact version.
How to install
mdr add flurdy/agent-skills/diagnose-bug@v1.1.2mdr add flurdy/agent-skills/diagnose-bug@sha256:0ca5793be7646ea1Pin 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.
[](https://markdownregistry.com/a/art_43q3sc5myovmoeap)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.1.2 latest | 2026-09-07 | 23d6b60 | 12,847 B | A | view · diff |
| v1.1.1 | 2026-09-04 | 801a002 | 12,834 B | A | view · diff |
| v1.1.0 | 2026-09-04 | ea0f1cd | 12,834 B | A | view · diff |
| v1.1.0 | 2026-07-21 | a359765 | 12,508 B | A | view · diff |
| v1.0.0 | 2026-07-18 | 38882a2 | 12,492 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 (12847 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
flurdy/agent-skills · 9 stars · license MIT · pushed 2026-09-23 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_43q3sc5myovmoeap GET https://markdownregistry.com/api/v1/resolve?ref=flurdy/agent-skills/diagnose-bug GET https://markdownregistry.com/api/v1/blob/0ca5793be7646ea15069993ebdb4cf8d1b1864d8563a9bf92e5e70b9a7a5a822
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.