
A battle-tested diagnosis loop for hard bugs and performance regressions: reproduce → minimise → hypothesise → instrument → fix → regression-test. Includes a human-in-the-loop helper script. From a working engineer's daily setup.
/diagnosing-bugs The dashboard gets slower every hour until someone restarts it
What you get
- A reproduce-minimize-hypothesize-instrument-fix-regression-test loop
- A helper script that keeps you in the loop without drowning you in output
- Redaction guidance so sensitive data never leaves your machine
Good fit
- Hard bugs and performance regressions
- "Works on my machine" mysteries
Not for
- Obvious bugs (systematic-debugging is faster)
- Writing new code from scratch
- Repository
- mattpocock/skills
- Stars
- 0
- Category
- Coding
- Skills inside
- 1
Exclusive content
Hosted on SkillStack — full markdown, yours after purchase.
--- name: diagnosing-bugs description: Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow. ---
Diagnosing Bugs
A discipline for hard bugs. Skip phases only when explicitly justified.…
Unlock the full content
Buy it once and keep it forever, or subscribe for access to everything.
Premium subscribers get this included.
Download & install
What's new: Initial SkillStack curated release: original MIT-licensed content repackaged as an install-ready ZIP with attribution.
Free for signed-in users.
1. Download the ZIP
Use the button above to download the packaged skill. It contains the SKILL.md plus all supporting files.
2. Unzip into your agent's skills folder
Extract the archive so that SKILL.md sits directly inside a folder named after the skill:
unzip diagnosing-bugs-v1.0.0.zip -d ~/.claude/skills/diagnosing-bugs/Skills folder per agent
- Claude Code
- ~/.claude/skills
- Cursor
- ~/.cursor/skills
- Codex
- ~/.codex/skills
- GitHub Copilot
- ~/.copilot/skills
3. Restart your agent
Your agent picks up the new skill automatically on next launch. Ask it what it can do.
FAQ
Is this one of Matt Pocock's agent skills?
Yes — its debugging method comes from Matt Pocock's open-source agent-skills collection (mattpocock/skills, MIT licensed). We've repackaged it as an install-ready ZIP with full attribution. For the full picture of his methodology, see our guide Matt Pocock's Agent Skills, Explained.
Reviews
Related skills
Systematic Debugging
obra/superpowers
Stop guessing at fixes. A 4-phase root-cause discipline (reproduce → isolate → hypothesize → verify) that forces your coding agent to find the real cause before touching code. The most-copied debugging skill in the Agent Skills ecosystem.
Claude Code · Codex · Cursor · Copilot +1
Git Workflow & Versioning
addyosmani/agent-skills
Branch strategy, commit discipline, PR hygiene, and release versioning for agent-driven development. Keeps AI-generated changes manageable, reviewable, and reversible at high speed.
Claude Code · Codex · Cursor · Copilot +1
Code Review & Quality
addyosmani/agent-skills
Multi-axis code review with severity gates (Critical/High/Medium/Low) across correctness, readability, architecture, security, and performance. By Addy Osmani (Google Chrome). Nothing merges without a verdict.
Claude Code · Codex · Cursor · Copilot
Readonly Question
Readonly Question
Ask anything about a codebase without changing a single file. A read-only /question mode for coding agents: evidence with file and line numbers, a proposed diff that is written out but never applied, and a verifiable 'No files were changed' footer. Understand the code first — change it only when you explicitly say so.
Claude Code · Codex · Cursor · Copilot +3