Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
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 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
…
The line at the top of this page pins the label git:20260821.05c0d52, 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_jfyqjz5ocxtsss23
GET https://markdownregistry.com/api/v1/resolve?ref=vodailocz/kilo-kit-mcp/diagnosing-bugs
GET https://markdownregistry.com/api/v1/blob/77f3cf31bc99b2f49af943222526531fcc9fc41d047626d3640e875e85af3e84
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.
vodailocz/kilo-kit-mcp · skills/agent-frameworks/agent-memory/SKILL.md · Use when implementing or managing persistent, hierarchical memory systems for AI agents. Covers cross-session state…
vodailocz/kilo-kit-mcp · skills/agent-frameworks/mcp-agent-patterns/SKILL.md · Use when integrating or optimizing Model Context Protocol (MCP) servers and clients. Keywords: MCP, Model Context…
vodailocz/kilo-kit-mcp · skills/agent-frameworks/workflow-state-machines/SKILL.md · Use when designing, implementing, or debugging complex agentic workflows using state machine patterns. Keywords: state…
vodailocz/kilo-kit-mcp · skills/ai-media/ai-multimodal/SKILL.md · Process and generate multimedia content using Google Gemini API. Capabilities include analyze audio files…
vodailocz/kilo-kit-mcp · skills/ai-media/screenshot/SKILL.md · Use when the user explicitly asks for a desktop or system screenshot (full screen, specific app or window, or a pixel…
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…
oyadotai/oya-browser · .agents/skills/diagnosing-bugs/SKILL.md · This skill should be used when diagnosing a reported bug, intermittent failure, stuck operation, or performance…
oyadotai/oya-browser · .claude/skills/diagnosing-bugs/SKILL.md · This skill should be used when diagnosing a reported bug, intermittent failure, stuck operation, or performance…
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…
