diagnosing-bugs SKILL.md skillA

This file is byte-identical to the first copy the registry indexed, one of 10 indexed copies. Same content hash, so the same checks give both the same grade.

diagnosing-bugs from hitesit/real-scientist-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add hitesit/real-scientist-skills/diagnosing-bugs@git:20261007.f3fc563

Pins git:20261007.f3fc563 in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
hitesit/real-scientist-skills
Path
skills/engineering/diagnosing-bugs/SKILL.md
Versions recorded
5
Latest version
git:20261007.f3fc563, committed Oct 7, 2026
First version recorded
Aug 15, 2026
Size
8,664 bytes
Repository stars
38
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

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

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

The exact contents, by fingerprint
mdr add hitesit/real-scientist-skills/diagnosing-bugs@sha256:849198df88cdb65f

The line at the top of this page pins the label git:20261007.f3fc563, 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_rg3ti6zcimgq4ajk.svg)](https://markdownregistry.com/a/art_rg3ti6zcimgq4ajk)

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: what changed in hitesit/real-scientist-skills/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 5 versions of this file, between Aug 15, 2026 and Oct 7, 2026, about one every 13 days.

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

versioncommittedcommitsizeaudit
git:20261007.f3fc563 latest2026-10-07 f3fc563 8,664 BA view · diff
git:20260917.d80fa0f2026-09-17 d80fa0f 8,530 BA view · diff
git:20260819.32165822026-08-19 3216582 8,529 BA view · diff
git:20260815.1dab9822026-08-15 1dab982 8,614 BA view · diff
git:20260815.fcf00712026-08-15 fcf0071 8,985 BA view

Copies

Copies in other repositories

15 files in 14 other repositories hold the exact bytes of one of this file's versions, each committed after this file had them: 8 hold the newest version and 7 an older one.

The 5 copies with the most stars, of 7 behind.

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

hitesit/real-scientist-skills · 38 stars · license MIT · pushed 2026-11-17 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_rg3ti6zcimgq4ajk
GET https://markdownregistry.com/api/v1/resolve?ref=hitesit/real-scientist-skills/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 hitesit/real-scientist-skills

AGENTS.md AGENTS.md file
hitesit/real-scientist-skills · AGENTS.md
git:20260713.697d4ce · audit B · 38 stars
CLAUDE.md CLAUDE.md file
hitesit/real-scientist-skills · CLAUDE.md
git:20261108.d0bb3f6 · audit A · 38 stars
chief-of-staff SKILL.md skill
hitesit/real-scientist-skills · customized/chief-of-staff/SKILL.md · Pursue a long-running goal in a single session by co-ordinating subagents.
git:20261108.d0bb3f6 · audit A · 38 stars
grilling SKILL.md skill
hitesit/real-scientist-skills · customized/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:20261108.d0bb3f6 · audit A · 38 stars
ask-matt SKILL.md skill
hitesit/real-scientist-skills · skills/engineering/ask-matt/SKILL.md · Ask which skill or flow fits your situation. A router over the skills in this repo.
git:20261006.954ee7f · audit A · 38 stars
code-review SKILL.md skill
hitesit/real-scientist-skills · skills/engineering/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:20261029.7739eae · audit A · 38 stars
codebase-design SKILL.md skill
hitesit/real-scientist-skills · skills/engineering/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:20260819.3216582 · audit A · 38 stars
domain-modeling SKILL.md skill
hitesit/real-scientist-skills · skills/engineering/domain-modeling/SKILL.md · Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md…
git:20260917.d80fa0f · audit A · 38 stars
grill-with-docs SKILL.md skill
hitesit/real-scientist-skills · skills/engineering/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:20260815.447ca70 · audit A · 38 stars
implement-spec SKILL.md skill
hitesit/real-scientist-skills · skills/engineering/implement-spec/SKILL.md · Implement the result of /to-spec and /to-tickets in code.
git:20261029.a496f55 · audit A · 38 stars
implement SKILL.md skill
hitesit/real-scientist-skills · skills/engineering/implement/SKILL.md · Implement a piece of work based on a spec or set of tickets.
git:20261007.6d6a5b9 · audit A · 38 stars
improve-codebase-architecture SKILL.md skill
hitesit/real-scientist-skills · skills/engineering/improve-codebase-architecture/SKILL.md · Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you…
git:20261029.7739eae · audit A · 38 stars

Every file in hitesit/real-scientist-skills

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.