diagnosing-bugs-zh SKILL.md skillA
diagnosing-bugs-zh from gongyijie85/mattpocock-skills-dsh-zh is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add gongyijie85/mattpocock-skills-dsh-zh/diagnosing-bugs-zh@git:20260910.0667b2cPins git:20260910.0667b2c in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- gongyijie85/mattpocock-skills-dsh-zh
- Path
skills/diagnosing-bugs-zh/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260910.0667b2c, committed Sep 10, 2026
- Size
- 8,883 bytes
- Repository stars
- 8
- License
- MIT
针对棘手的 bug 和性能 regression 的诊断回路。当用户说 "diagnose"/"debug this",或报告某样东西 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 针对棘手 bug 的纪律。只有在明确有理有据时才跳过某些 phase。 探索 codebase 时,阅读 `CONTEXT.md`(如果存在)以获得相关模块清晰的 mental model(心智模型),并检查你正在接触区域的 ADR。 ## Redact(脱敏) 本 skill 要求你展示命令、输出和捕获的产物。**先对每个 secret 脱敏** — 用 `<REDACTED>` 代替。针对 env vars 构建回路,这样凭据留在环境中,而不是留在你展示的内容里。捕获的产物带有 auth headers:只引用携带信号的几行。 如果脱敏后的输出不足以诊断 bug,直说并询问用户。 ## Phase 1 — 构建反馈回路 **这才是本 skill 的核心。** 其他一切都是机械性的。如果你有一个针对该 bug 的**紧致**通过/失败信号 — 一个能在_这个_ bug 上变红的信号 — 你就会找到原因;bisection(二分)、假设检验和 instrumentation 都只是在消费它。如果你没有这样的信号,再怎么盯着代码看也救不了你。 在这里投入不成比例的努力。**要激进。要有创造力。拒绝放弃。** ### 构建反馈回路的方法 — 大致按这个顺序尝试 1. **失败的测试** — 在任何能触达 bug 的 seam 上 — unit、integration、e2e。 2. **Curl / HTTP 脚本** — 针对运行中的 dev server。 3. **CLI 调用** — 用 fixture 输入,把 stdout 与已知良好的快照做 diff。 4. **无头浏览器脚本**(Playwright / Puppeteer)— 驱动 UI,在 DOM/console/network 上做断言。 5. **重放捕获的 trace。** 把真实的网络请求 / payload / 事件日志保存到磁盘;在隔离环境中通过代码路径重放它。 6. **一次性 harness。** 启动系统的一个最小子集(一个 service,依赖用 mock),用一次函数调用触发 bug 代码路径。 7. **Property / fuzz 回路。** 如果 bug 是 "sometimes wrong output(偶尔输出错误)",运行 1000 个随机输入,寻找失败模式。 8. **Bisection harness。** 如果 bug 出现在两个已知状态(commit、数据集、版本)之间,把 "boot at state X, check, repeat(在状态 X 启动、检查、重复)" 自动化,这样你就可以对它 `git bisect run`。 …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_4ly3w3wcrl6justh/463f152a02738059ab5d0f9843cf1da5791f8fd56dd5788f59dd8a57ec5587b1.json
Then /plugin install diagnosing-bugs-zh@markdownregistry-4ly3w3wcrl6justh in Claude Code. It installs git:20260910.0667b2c, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add gongyijie85/mattpocock-skills-dsh-zh/diagnosing-bugs-zh@sha256:463f152a02738059The line at the top of this page pins the label git:20260910.0667b2c, 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.
[](https://markdownregistry.com/a/art_4ly3w3wcrl6justh)
2 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in gongyijie85/mattpocock-skills-dsh-zh/diagnosing-bugs-zh 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-zh from somewhere else? Ask it: where did my diagnosing-bugs-zh 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 Sep 10, 2026.
Watch this file (sign in, one email per new version)
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.
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.
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.
Installed this file, say at .claude/skills/diagnosing-bugs-zh/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
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
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (8883 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
gongyijie85/mattpocock-skills-dsh-zh · 8 stars · license MIT · pushed 2026-11-18 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_4ly3w3wcrl6justh GET https://markdownregistry.com/api/v1/resolve?ref=gongyijie85/mattpocock-skills-dsh-zh/diagnosing-bugs-zh GET https://markdownregistry.com/api/v1/blob/463f152a02738059ab5d0f9843cf1da5791f8fd56dd5788f59dd8a57ec5587b1
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.