skills sourced live from GitHub · all skills listed are free · each skill is provided under its author's license.
home / Coding / Diagnosing Bugs Skill by @mattpocock
The skill is the skills/engineering/diagnosing-bugs folder inside that repository. Copy it into the folder your agent loads skills from; check your agent's documentation for where that is.
Diagnosis loop for hard bugs and performance regressions.
A disciplined loop for hard bugs and performance regressions. It starts by building a fast, reliable way to reproduce the problem and only then moves toward a fix, with advice for non-deterministic bugs and for when you truly cannot reproduce one.
The original SKILL.md is organised into these sections:
Written and maintained by @mattpocock. It is published under the MIT license, which allows reuse with attribution. See the author profile. SkillDirectory does not claim authorship: this page adds our own review and links back to the original, and the skill's text belongs to its author.
# 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 …
Excerpt only, quoted from the author's repository. Open the repository for the complete file.