diagnosing-bugs SKILL.md skillA
diagnosing-bugs from shumingyang-opencode/mattpocock-skills-zh-tw is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add shumingyang-opencode/mattpocock-skills-zh-tw/diagnosing-bugs@git:20261007.5695450Pins git:20261007.5695450 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- shumingyang-opencode/mattpocock-skills-zh-tw
- Path
skills/engineering/diagnosing-bugs/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261007.5695450, committed Oct 7, 2026
- First version recorded
- Jun 12, 2026
- Size
- 8,525 bytes
- Repository stars
- 3
- License
- MIT
硬 bug 與效能回歸的診斷迴圈。當使用者說「diagnose」/「debug this」，或回報東西壞了/拋錯/失敗/很慢時使用。.
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
# 診斷 Bug 一套應付硬 bug 的紀律。只有明確證成時才可跳過階段。 探索程式碼時，先讀 `GLOSSARY.md`（如果存在）以取得相關模組的清晰心智模型，並檢查你要觸及的區域中的 ADR。 ## 第一階段——建立回饋迴圈 **這就是本技能的核心。** 其他一切都是機械性作業。如果你對這個 bug 有一個**緊密**的通過/失敗訊號——一個會因為_這個_ bug 而變紅的訊號——你就會找到原因；二分、假設檢驗與插樁都只是在消耗它。如果你沒有這樣的訊號，再怎麼瞪著程式碼看也救不了你。 在這裡投入不成比例的精力。**要積極。要有創意。拒絕放棄。** ### 建立回饋迴圈的方法——大致依此順序嘗試 1. **失敗測試**，在任何觸及 bug 的接縫——單元、整合、e2e。 2. **curl / HTTP 腳本**，對著正在執行的開發伺服器。 3. **CLI 呼叫**，搭配固定裝置輸入，把 stdout 跟已知良好快照做 diff。 4. **無頭瀏覽器腳本**（Playwright / Puppeteer）——驅動 UI，對 DOM / 主控台 / 網路做斷言。 5. **重播擷取的追蹤**。把真實的網路請求 / payload / 事件日誌存到磁碟；在隔離環境中透過程式碼路徑重播。 6. **一次性測試架**。啟動系統的最小子集合（一個服務、模擬過的相依），用單一函式呼叫去觸發 bug 的程式碼路徑。 7. **屬性 / 模糊測試迴圈**。如果 bug 是「輸出偶爾錯誤」，跑 1000 個隨機輸入，找出失敗模式。 8. **二分測試架**。如果 bug 出現在兩個已知狀態之間（commit、資料集、版本），自動化「在狀態 X 啟動、檢查、重複」，讓你能 `git bisect run`。 9. **差異迴圈**。把相同輸入跑過舊版 vs 新版（或兩種設定），diff 輸出。 10. **HITL bash 腳本**。最後手段。如果必須由人點擊，用 `scripts/hitl-loop.template.sh` 驅動_他們_，讓迴圈仍然結構化。擷取的輸出會回饋給你。 建立正確的回饋迴圈，bug 就完成九成了。 ### 收緊迴圈 把迴圈當產品來經營。一旦有了_一個_迴圈，就**收緊**它： - 能不能讓它更快？（快取設定、跳過無關的初始化、縮小測試範圍。） - 能不能讓訊號更銳利？（斷言具體症狀，而不是「沒有崩潰」。） - 能不能讓它更確定？（釘住時間、播種 RNG、隔離檔案系統、凍結網路。） 一個要花 30 秒的搖擺迴圈只比沒有迴圈好一點點；一個 2 秒且確定的是緊密的——這是除錯的超能力。 ### 非確定性 bug …
Read the whole file at its exact version.
How to install
mdr add shumingyang-opencode/mattpocock-skills-zh-tw/diagnosing-bugs@sha256:704e6bf7d98b1b51The line at the top of this page pins the label git:20261007.5695450, 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_n6szumk2twft4t7y)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Jun 12, 2026 and Oct 7, 2026, about one every 29 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261007.5695450 latest | 2026-10-07 | 5695450 | 8,525 B | A | view · diff |
| git:20260806.5bfe60b | 2026-08-06 | 5bfe60b | 8,524 B | A | view · diff |
| git:20260617.ee8bae4 | 2026-06-17 | ee8bae4 | 8,536 B | A | view · diff |
| git:20260617.bc4cf90 | 2026-06-17 | bc4cf90 | 8,680 B | A | view · diff |
| git:20260612.221ffca | 2026-06-12 | 221ffca | 7,176 B | A | view |
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 (8525 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
shumingyang-opencode/mattpocock-skills-zh-tw · 3 stars · license MIT · pushed 2026-10-07 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_n6szumk2twft4t7y GET https://markdownregistry.com/api/v1/resolve?ref=shumingyang-opencode/mattpocock-skills-zh-tw/diagnosing-bugs GET https://markdownregistry.com/api/v1/blob/704e6bf7d98b1b5162b6ed2859e1f0d36f2e0361cae5a84fd75171512aff4d41
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 shumingyang-opencode/mattpocock-skills-zh-tw
Every file in shumingyang-opencode/mattpocock-skills-zh-tw