Skip to content
Skill

Diagnosing bugs

Diagnosis loop for hard bugs and performance regressions

Install
Scripts
shell
Platforms
Claude Code, Codex, Cursor
GitHub stars
326K
Last commit
today
License
MIT
Listing updated
today

When your agent uses it

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.

From the skill's SKILL.md. Your agent reads this description to decide when to load the skill.

What it can access

From a static check of its 3 files (10 KB) on GitHub on 17 November 2026. Nothing was run. Read the files before you install a skill: it can tell your agent to run anything its tools allow.

Install

Copy the skill folder to ~/.claude/skills/diagnosing-bugs to use it in all your projects:

tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/mattpocock/skills.git "$tmp" &&
mkdir -p ~/.claude/skills &&
rm -rf ~/.claude/skills/diagnosing-bugs &&
cp -R "$tmp/skills/engineering/diagnosing-bugs" ~/.claude/skills/diagnosing-bugs &&
rm -rf "$tmp"

For one project only, put the folder in .claude/skills/diagnosing-bugs inside it instead.

Claude Code docs on skills

Copy the skill folder to ~/.agents/skills/diagnosing-bugs to use it in every repository:

tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/mattpocock/skills.git "$tmp" &&
mkdir -p ~/.agents/skills &&
rm -rf ~/.agents/skills/diagnosing-bugs &&
cp -R "$tmp/skills/engineering/diagnosing-bugs" ~/.agents/skills/diagnosing-bugs &&
rm -rf "$tmp"

For one repository only, put the folder in .agents/skills/diagnosing-bugs inside it instead.

Codex docs on skills

Copy the skill folder to ~/.cursor/skills/diagnosing-bugs to use it in every project:

tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/mattpocock/skills.git "$tmp" &&
mkdir -p ~/.cursor/skills &&
rm -rf ~/.cursor/skills/diagnosing-bugs &&
cp -R "$tmp/skills/engineering/diagnosing-bugs" ~/.cursor/skills/diagnosing-bugs &&
rm -rf "$tmp"

For one project only, put the folder in .cursor/skills/diagnosing-bugs inside it instead.

Cursor docs on skills

Run in a terminal (add --scope workspace to install it for the current workspace only):

gemini skills install https://github.com/mattpocock/skills.git --path skills/engineering/diagnosing-bugs

Or copy the folder to ~/.gemini/skills/diagnosing-bugs yourself.

Gemini CLI docs on skills

For GitHub Copilot in VS Code, copy the skill folder to ~/.copilot/skills/diagnosing-bugs:

tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/mattpocock/skills.git "$tmp" &&
mkdir -p ~/.copilot/skills &&
rm -rf ~/.copilot/skills/diagnosing-bugs &&
cp -R "$tmp/skills/engineering/diagnosing-bugs" ~/.copilot/skills/diagnosing-bugs &&
rm -rf "$tmp"

For one project only, put the folder in .github/skills/diagnosing-bugs inside it instead.

VS Code docs on skills

Get the folder:

git clone --depth 1 https://github.com/mattpocock/skills.git

Then copy skills/skills/engineering/diagnosing-bugs into your agent's skills folder as diagnosing-bugs. Agents that support SKILL.md read one folder per skill.

The SKILL.md format

Diagnosing bugs FAQ

How do I install Diagnosing bugs in Claude Code?

Copy the skill folder from GitHub to ~/.claude/skills/diagnosing-bugs to use it in all your projects, or to .claude/skills/diagnosing-bugs in one project.

Does Diagnosing bugs run scripts?

Yes. It runs shell scripts. No network calls were found in its scripts. This comes from a static check of the files on GitHub; nothing was run. Read the files before you install it.

Which AI agents can use Diagnosing bugs?

Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf and Goose. Each reads skills in the SKILL.md format from its own folder; the install steps on this page list them.

More from mattpocock/skills

  1. Ask which skill or flow fits your situation

    • Open source
    • 326K GitHub stars
  2. Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's docu

    • Open source
    • 326K GitHub stars
    • Developer tools
  3. Shared vocabulary for designing deep modules

    • Open source
    • 326K GitHub stars
    • Design and media
  4. Build and sharpen a project's domain model

    • Open source
    • 326K GitHub stars
  5. A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.

    • Open source
    • 326K GitHub stars
  6. Implement a piece of work based on a spec or set of tickets.

    • Open source
    • 326K GitHub stars