diagnosing-bugs SKILL.md skillA

The newest version of a file that held these bytes earlier

diagnosing-bugs in philoserf/claude-code-config is at git:20261110.5c2533d (Nov 10, 2026), graded A.

mdr add philoserf/claude-code-config/diagnosing-bugs@git:20261110.5c2533d

This copy is 1 version behind it. See what changed · install this older copy instead

This line moves to the next version by itself within about an hour of that file saving one. A copy already installed stays as it is until you update it.

diagnosing-bugs from erumkatzwan/agentic-product-starter is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
erumkatzwan/agentic-product-starter
Path
.agents/skills/diagnosing-bugs/SKILL.md
Versions recorded
1
Latest version
git:20261114.575c5a5, committed Nov 14, 2026
Size
8,664 bytes
Repository stars
4
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` (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

This older copy, pinned
mdr add erumkatzwan/agentic-product-starter/diagnosing-bugs@git:20261114.575c5a5

Pins git:20261114.575c5a5 in mdr.lock, 1 version behind the newest at the top of this page.

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_5zzluz5qo3z7o3eq/849198df88cdb65fd0d97236604c1fca7ff2f22d2f705f9724a800d0266b118d.json

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

The exact contents, by fingerprint
mdr add erumkatzwan/agentic-product-starter/diagnosing-bugs@sha256:849198df88cdb65f

The older copy line above pins the label git:20261114.575c5a5, 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_5zzluz5qo3z7o3eq.svg)](https://markdownregistry.com/a/art_5zzluz5qo3z7o3eq)

2 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: get me the newest philoserf/claude-code-config/diagnosing-bugs, and what changed since 849198d? 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 1 version of this file, committed on Nov 14, 2026.

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

versioncommittedcommitsizeaudit
git:20261114.575c5a5 latest2026-11-14 575c5a5 8,664 BA view

Copies

The newest version, then this copy

Newest: git:20261110.5c2533d of diagnosing-bugs in philoserf/claude-code-config (skills/diagnosing-bugs/SKILL.md), graded A.

This copy: byte for byte that file's version git:20261109.97997e2, which it committed on Nov 9, 2026, before this repository did; graded A, 1 version behind.

See what changed since these bytes · ask your agent

Matched on the exact bytes and the commit dates, nothing else. It does not say who wrote the file or where this repository got it.

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 (8664 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

erumkatzwan/agentic-product-starter · 4 stars · license MIT · pushed 2026-11-17 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_5zzluz5qo3z7o3eq
GET https://markdownregistry.com/api/v1/resolve?ref=erumkatzwan/agentic-product-starter/diagnosing-bugs
GET https://markdownregistry.com/api/v1/blob/849198df88cdb65fd0d97236604c1fca7ff2f22d2f705f9724a800d0266b118d

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 erumkatzwan/agentic-product-starter

accessibility SKILL.md skill
erumkatzwan/agentic-product-starter · .agents/skills/accessibility/SKILL.md · Use when building or changing any screen, component or colour, when an accessibility check is red, before a release, or…
git:20261115.e585cb8 · audit A · 4 stars
architecture-decisions SKILL.md skill
erumkatzwan/agentic-product-starter · .agents/skills/architecture-decisions/SKILL.md · Use before building anything that changes how parts of the system fit together, and whenever a decision is hard to…
git:20261114.a576410 · audit A · 4 stars
ask-matt SKILL.md skill
erumkatzwan/agentic-product-starter · .agents/skills/ask-matt/SKILL.md · Ask which skill or flow fits your situation. A router over the skills in this repo.
git:20261114.575c5a5 · audit A · 4 stars
code-review SKILL.md skill
erumkatzwan/agentic-product-starter · .agents/skills/code-review/SKILL.md · Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code…
git:20261114.575c5a5 · audit A · 4 stars
codebase-design SKILL.md skill
erumkatzwan/agentic-product-starter · .agents/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:20261114.575c5a5 · audit A · 4 stars
domain-modeling SKILL.md skill
erumkatzwan/agentic-product-starter · .agents/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:20261114.575c5a5 · audit A · 4 stars
dora-metrics SKILL.md skill
erumkatzwan/agentic-product-starter · .agents/skills/dora-metrics/SKILL.md · Use when someone asks how the team is delivering, wants DORA metrics or the delivery dashboard explained or changed…
git:20261115.6fbcf79 · audit A · 4 stars
grill-me SKILL.md skill
erumkatzwan/agentic-product-starter · .agents/skills/grill-me/SKILL.md · A relentless interview to sharpen a plan or design.
git:20261114.575c5a5 · audit B · 4 stars
grill-with-docs SKILL.md skill
erumkatzwan/agentic-product-starter · .agents/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.
git:20261114.575c5a5 · audit A · 4 stars
grilling SKILL.md skill
erumkatzwan/agentic-product-starter · .agents/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…
git:20261114.575c5a5 · audit A · 4 stars
handoff SKILL.md skill
erumkatzwan/agentic-product-starter · .agents/skills/handoff/SKILL.md · Compact the current conversation into a handoff document for another agent to pick up.
git:20261114.575c5a5 · audit A · 4 stars
implement-spec SKILL.md skill
erumkatzwan/agentic-product-starter · .agents/skills/implement-spec/SKILL.md · Implement the result of /to-spec and /to-tickets in code.
git:20261114.575c5a5 · audit A · 4 stars

Every file in erumkatzwan/agentic-product-starter

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.

Kept in .agents/skills, the folder Codex reads. More agent skills for Codex.