diagnosing-bugs SKILL.md skillA

diagnosing-bugs from philoserf/claude-code-config is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add philoserf/claude-code-config/diagnosing-bugs@git:20261110.5c2533d

Pins git:20261110.5c2533d in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
philoserf/claude-code-config
Path
skills/diagnosing-bugs/SKILL.md
Versions recorded
2
Latest version
git:20261110.5c2533d, committed Nov 10, 2026
First version recorded
Nov 9, 2026
Size
8,691 bytes
Repository stars
14
License
MIT

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 `GLOSSARY.md` (at the root or in `docs/`, 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
…

Read the whole file at its exact version.

How to install

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_lotz2ynfq72k2xx6/f9dba29f15fafe83b60226b23dd143c0c52ed0b227312e52d1425f881e2ea6df.json

Then /plugin install diagnosing-bugs@markdownregistry-lotz2ynfq72k2xx6 in Claude Code. It installs git:20261110.5c2533d, the one graded A here, pinned to the commit it was graded at, and leaves it there.

The exact contents, by fingerprint
mdr add philoserf/claude-code-config/diagnosing-bugs@sha256:f9dba29f15fafe83

The line at the top of this page pins the label git:20261110.5c2533d, 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.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_lotz2ynfq72k2xx6.svg)](https://markdownregistry.com/a/art_lotz2ynfq72k2xx6)

3 badge image fetches in 30 days. What the badge shows.

Ask from your agent
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry

Then ask it: what changed in philoserf/claude-code-config/diagnosing-bugs since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.

Got a copy of diagnosing-bugs from somewhere else? Ask it: where did my diagnosing-bugs come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.

Versions

The registry has recorded 2 versions of this file, between Nov 9, 2026 and Nov 10, 2026, about one every day.

Watch this file (sign in, one email per new version)

versioncommittedcommitsizeaudit
git:20261110.5c2533d latest2026-11-10 5c2533d 8,691 BA view · diff
git:20261109.97997e22026-11-09 97997e2 8,664 BA view

Copies

Copies in other repositories

1 file in 1 other repository holds the exact bytes of one of this file's versions, each committed after this file had them: it holds an older version.

A copy does not update when this file does. Whoever holds one can learn which version it is with the Check your copy box below, or by asking their agent. Matched on exact bytes and commit dates only.

Keep it current by itself, install once

Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

Install on GitHub

It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.

Keep it current by itself

Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml

It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.

Check a whole project

From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies

In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies

No sha256sum on your machine? shasum -a 256 prints the same lines.

Audit of the latest version

A  17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • pass: Frontmatter block present
  • pass: Frontmatter declares a name
  • pass: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (8691 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

GitHub

philoserf/claude-code-config · 14 stars · license MIT · pushed 2026-11-16 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_lotz2ynfq72k2xx6
GET https://markdownregistry.com/api/v1/resolve?ref=philoserf/claude-code-config/diagnosing-bugs
GET https://markdownregistry.com/api/v1/blob/f9dba29f15fafe83b60226b23dd143c0c52ed0b227312e52d1425f881e2ea6df

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 philoserf/claude-code-config

CLAUDE.md@.claude CLAUDE.md file
philoserf/claude-code-config · .claude/CLAUDE.md
git:20261030.fb6894c · audit A · 14 stars
cc-release-review SKILL.md skill
philoserf/claude-code-config · .claude/skills/cc-release-review/SKILL.md · Reviews Claude Code release notes and recommends config updates. Use when asking "what changed in the CLI/release"…
git:20260925.b906bd9 · audit B · 14 stars
verify SKILL.md skill
philoserf/claude-code-config · .claude/skills/verify/SKILL.md · Runs this repo's pre-commit gate — `task`, which formats markdown and JSON and runs the test suites. Use right before…
git:20261026.7b9ba83 · audit B · 14 stars
CLAUDE.md CLAUDE.md file
philoserf/claude-code-config · CLAUDE.md
git:20261111.db534dc · audit A · 14 stars
assisted-log SKILL.md skill
philoserf/claude-code-config · skills/assisted-log/SKILL.md · Writes a concise summary of this session's work into today's daily journal under ### Assisted. Use only when the user…
git:20261105.1424bed · audit A · 14 stars
code-theory SKILL.md skill
philoserf/claude-code-config · skills/code-theory/SKILL.md · Builds a Naur-style theory of a codebase — the understanding needed to change it without damaging its conceptual…
git:20261109.6ae502c · audit B · 14 stars
code-walkthrough SKILL.md skill
philoserf/claude-code-config · skills/code-walkthrough/SKILL.md · Reads source code and produces a linear walkthrough document. Use when explaining how code works, creating…
git:20261110.9b626b2 · audit B · 14 stars
codebase-design SKILL.md skill
philoserf/claude-code-config · 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…
git:20261109.bdfab82 · audit A · 14 stars
domain-modeling SKILL.md skill
philoserf/claude-code-config · skills/domain-modeling/SKILL.md · Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md…
git:20261110.5c2533d · audit A · 14 stars
downloads-triage SKILL.md skill
philoserf/claude-code-config · skills/downloads-triage/SKILL.md · Files what has piled up in ~/Downloads, iCloud Drive's Downloads, and ~/Desktop, sending each item to the Documents…
git:20261103.b9d1e10 · audit A · 14 stars
editor SKILL.md skill
philoserf/claude-code-config · skills/editor/SKILL.md · Copy edits prose while preserving voice and register, and gives magazine-editor notes on non-fiction. Use when asked to…
git:20261101.83315e4 · audit A · 14 stars
grill-me SKILL.md skill
philoserf/claude-code-config · skills/grill-me/SKILL.md · A relentless interview to sharpen a plan or design.
git:20261109.97997e2 · audit B · 14 stars

Every file in philoserf/claude-code-config

Other files named diagnosing-bugs

diagnosing-bugs SKILL.md skill
mattpocock/skills · skills/engineering/diagnosing-bugs/SKILL.md · Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports…
git:20261007.f3fc563 · audit A · 327,521 stars
diagnosing-bugs SKILL.md skill
vinvcn/mattpocock-skills-zh-cn · skills/engineering/diagnosing-bugs/SKILL.md · 面向棘手缺陷和性能回退的诊断循环。适用于用户说 “diagnose” / “debug this”,或报告某些东西 broken、throwing、failing、slow 时。
git:20261028.c48fd4a · audit A · 5,886 stars
diagnosing-bugs SKILL.md skill
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…
git:20261028.4eb8b2a · audit A · 559 stars
diagnosing-bugs SKILL.md skill
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…
git:20261009.b4e20e9 · audit A · 516 stars
diagnosing-bugs SKILL.md skill
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…
git:20261022.752a38b · audit A · 370 stars
diagnosing-bugs SKILL.md skill
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…
git:20261021.2ea469d · audit A · 349 stars
diagnosing-bugs SKILL.md skill
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…
git:20261021.2ea469d · audit A · 349 stars
diagnosing-bugs SKILL.md skill
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…
git:20261104.30b60de · audit A · 130 stars

Browse by kind, by grade A, or by owner.