diagnosing-bugs SKILL.md skillA
This file is byte-identical to the first copy the registry indexed, one of 7 indexed copies. Same content hash, so the same checks give both the same grade.
diagnosing-bugs from tiagocolombo/hallmark is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add tiagocolombo/hallmark/diagnosing-bugs@git:20261012.e09dd11Pins git:20261012.e09dd11 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- tiagocolombo/hallmark
- Path
extensions/mattpocock/skills/diagnosing-bugs/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261012.e09dd11, committed Oct 12, 2026
- Size
- 8,664 bytes
- Repository stars
- 9
- 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
mdr add tiagocolombo/hallmark/diagnosing-bugs@sha256:849198df88cdb65fThe line at the top of this page pins the label git:20261012.e09dd11, 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_4r552z7oxviv4bl7)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 12, 2026.
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 (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
tiagocolombo/hallmark · 9 stars · license MIT · pushed 2026-11-01 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_4r552z7oxviv4bl7 GET https://markdownregistry.com/api/v1/resolve?ref=tiagocolombo/hallmark/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 tiagocolombo/hallmark
Every file in tiagocolombo/hallmark