Diagnose difficult or uncertain bugs and performance regressions with a reproducible feedback loop. Use when investigation is needed beyond an evident local fix.
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
# Diagnose bugs and performance regressions
Start with the user’s symptom, relevant source, and available evidence. For an evident local defect, make the scoped fix and verify it directly. Use a deeper investigation loop when the cause is uncertain, reproduction is intermittent, or earlier fixes failed. Consult the project’s glossary (`GLOSSARY.md`, `CONTEXT.md`, or its equivalent) and ADRs when they affect the area.
## Establish useful evidence
Choose the smallest reliable signal that reaches the actual failure. Useful options include an existing or targeted regression test, a local HTTP request, a CLI fixture, a browser interaction, replaying a captured trace, a temporary harness, bounded seeded fuzzing, bisection, or comparing matched versions. Confirm the signal distinguishes the reported symptom from an unrelated failure.
For a reproduction that requires human interaction, adapt [the human-in-the-loop template](scripts/hitl-loop.template.sh). Capture observations only; leave signing in and entering credentials to the user.
…
The line at the top of this page pins the label git:20261011.ef64499, 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.
GET https://markdownregistry.com/api/v1/artifacts/art_oz72rpesojuhp6rj
GET https://markdownregistry.com/api/v1/resolve?ref=transitive-bullshit/skills/diagnosing-bugs
GET https://markdownregistry.com/api/v1/blob/b6dec1fdda6ef60f751306cd7be595589bdf4232225f305500f93a400a705dc0
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.
transitive-bullshit/skills · provenance/history/2026-10-11-removed/resolving-merge-conflicts/SKILL.md · Use when you need to resolve an in-progress git merge/rebase conflict.
transitive-bullshit/skills · provenance/upstream/auto-research/skill/SKILL.md · Run fast, progressive experiments to map tunable parameters and their effects. Use when optimizing code, prompts…
transitive-bullshit/skills · provenance/upstream/better-colors/SKILL.md · Helps you build and check a color system for your project. It generates palettes, names semantic tokens, converts…
transitive-bullshit/skills · provenance/upstream/better-layout/SKILL.md · Helps with grouping, alignment, reading order, responsive structure and room for translated text, so a layout holds up…
transitive-bullshit/skills · provenance/upstream/better-typography/SKILL.md · Sets and reviews how text renders in your product, from the type scale and spacing to font features, wrapping…
transitive-bullshit/skills · provenance/upstream/better-ui/SKILL.md · Polishes the surfaces, icons and motion in your project with exact values for border radius, optical alignment…
transitive-bullshit/skills · provenance/upstream/better-writing/SKILL.md · Writes and reviews your interface copy, from labels and errors to empty states and confirmations, so it matches your…
transitive-bullshit/skills · provenance/upstream/claude/skill/SKILL.md · Use Claude Code as an independent `claude -p` subagent when the user explicitly asks for Claude, wants a second-agent…
transitive-bullshit/skills · provenance/upstream/codebase-design/skill/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/diagnosing-bugs/SKILL.md · Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports…
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…
jellydn/my-ai-tools · skills/diagnosing-bugs/SKILL.md · Build a tight, red-capable feedback loop before diagnosing failures, then minimize, test ranked hypotheses, and lock…
jellydn/my-ai-tools · configs/amp/plugins/my-ai-tools-skills/skills/diagnosing-bugs/SKILL.md · Build a tight, red-capable feedback loop before diagnosing failures, then minimize, test ranked hypotheses, and lock…
gtapps/claude-code-hermit · plugins/hermitd-dev/skills/diagnosing-bugs/SKILL.md · Diagnosis loop for hard bugs and performance regressions. Builds a red-capable feedback loop and runs it before…
gtapps/hermitd · plugins/hermitd-dev/skills/diagnosing-bugs/SKILL.md · Diagnosis loop for hard bugs and performance regressions. Builds a red-capable feedback loop and runs it before…