$ skilldirectory
— zsh — registry.skilldirectory.dev
skill library blog

home / Coding / Diagnosing Bugs Skill by @mattpocock

Diagnosing Bugs Skill by @mattpocock

FREE
github stars★ 3,15,437updatedOct 2026repo@mattpocock
$git clone https://github.com/mattpocock/skills

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.

Read the opening of the original SKILL.md
# 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.