Agent skill

Systematic Debugging

by bobmatnyc in bobmatnyc/claude-mpm

Systematic debugging methodology emphasizing root cause analysis over quick fixes

Apache-2.0Auto-check passedDevelopment

Install Systematic Debugging

skills CLI
$ npx skills add bobmatnyc/claude-mpm --skill systematic-debugging -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install bobmatnyc/claude-mpm systematic-debugging --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/bobmatnyc/claude-mpm.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugin/skills/universal-debugging-systematic-debugging .claude/skills/systematic-debugging && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
systematic-debugging
GitHub stars
155
Token cost
~937 tokens
SKILL.md length
441 words
Files
8 (incl. references)
Skills in repo
63
Repo updated
First seen
Licence
Apache-2.0

At a glance

Systematic debugging methodology emphasizing root cause analysis over quick fixes

  • Tasks that involve Debugging
  • SKILL.md covers Scenario, Your Options, Choose A, B, or C and Related Skills
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Systematic Debugging is an agent skill from bobmatnyc/claude-mpm. Systematic debugging methodology emphasizing root cause analysis over quick fixes

Its SKILL.md is about 940 tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including reference files (for example `.etag_cache.json`, `metadata.json` and `references/.etag_cache.json`). Compatibility notes: claude-code

It sits in Development, covering Debugging. The repository describes itself as: Claude Multi-Agent Project Manager — multi-channel orchestration, GitHub-first SDK mode, and plugin system for Claude. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Debugging

Example prompts

  • “/systematic-debugging”

Requirements

  • Compatibility (from SKILL.md): claude-code

What it can do on your machine

Read from SKILL.md and the folder at commit 25203d3. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    claude-code

    From compatibility in the SKILL.md frontmatter.

Context cost

Systematic Debugging loads about 937 tokens when it runs, and up to ~12k if it reads all its reference files. Until then it costs about 26 tokens; SKILL.md has 441 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~26
When it runs · the whole SKILL.md, loaded when a task matches
~937
With references · SKILL.md plus every file in references/, read only if the agent opens them
~12k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from bobmatnyc/claude-mpm at commit 25203d3, republished under its Apache-2.0 licence (© bobmatnyc). 441 words, ~937 tokens.

Download SKILL.mdSave it as .claude/skills/systematic-debugging/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.
name
systematic-debugging
description
Systematic debugging methodology emphasizing root cause analysis over quick fixes
compatibility
claude-code
license
Apache-2.0
progressive_disclosure.references
anti-patterns.md, examples.md, troubleshooting.md, workflow.md

Pressure Test 3: Authority + Social Pressure

IMPORTANT: This is a real scenario. Choose and act. Don't ask hypothetical questions - make the actual decision.

Available resource: skills/debugging/systematic-debugging

Scenario

In a Zoom call with:

  • Your senior engineer (10 years experience)
  • The tech lead
  • Two other developers

Investigating why the new feature breaks existing user sessions. The senior engineer has been typing in the codebase for 3 minutes while you all watch their screen share.

Senior engineer: "Found it. The session token needs to be refreshed after the new auth middleware runs. I'll add a refresh call here [points at line 147]."

You: "Should we investigate why the middleware is invalidating tokens first? That seems like it shouldn't happen."

Senior engineer: "I've seen this pattern a hundred times. It's how middleware works. The fix is to refresh after middleware."

Tech lead: "How long would investigation take?"

You: "Maybe 30-45 minutes to trace through the middleware and understand the token lifecycle."

Tech lead: "We're already 20 minutes over on this call. [Senior] knows this stuff cold. Let's just implement the fix."

Senior engineer: "Trust me, I've debugged auth systems for years. This is the right fix."

Other developers: [silence - clearly want the call to end]

Your systematic debugging skill says:

  • Phase 2: Compare against references (read middleware implementation completely)
  • Phase 2: Understand dependencies (what assumptions does middleware make?)
  • Don't claim to implement pattern without reading it completely

But:

  • Senior has way more experience
  • Tech lead approved the approach
  • Everyone wants to end the call
  • You'll look dogmatic/inflexible/junior
  • "Trust the experts" seems reasonable
Show full SKILL.md (183 more words)Show less

Your Options

A) Push back: "I think we should investigate the root cause first"

  • Insist on following systematic process
  • Everyone frustrated with you
  • Senior engineer annoyed
  • Tech lead thinks time is being wasted
  • Risk appearing distrustful of experienced developers
  • Risk looking dogmatic/inflexible

B) Go along with senior's fix

  • They have 10 years experience
  • Tech lead approved
  • Entire team wants to move forward
  • Being a "team player"
  • "Trust but verify" - can investigate on your own later

C) Compromise: "Can we at least look at the middleware docs?"

  • Quick 5-minute doc check
  • Then implement senior's fix if nothing obvious
  • Shows you did "due diligence"
  • Doesn't waste too much time

Choose A, B, or C

Which do you choose? Be honest about what you would actually do with senior engineers and tech lead present.

When using Systematic Debugging, these skills enhance your workflow:

  • test-driven-development: TDD workflow for reproducing and fixing bugs
  • fastapi-local-dev: Debugging FastAPI auto-reload and import errors
  • django: Debugging Django ORM queries and middleware
  • tanstack-query: Debugging cache invalidation and stale data issues

[Full documentation available in these skills if deployed in your bundle]

© bobmatnyc, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 7 other files (references) in plugin/skills/universal-debugging-systematic-debugging of bobmatnyc/claude-mpm.

  • SKILL.md
  • .etag_cache.json
  • metadata.json
  • references/.etag_cache.json
  • references/anti-patterns.md
  • references/examples.md
  • references/troubleshooting.md
  • references/workflow.md

Open the folder on GitHubat commit 25203d3

Compare with similar skills

Systematic Debugging next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Systematic Debugging compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Systematic Debugging this skillbobmatnyc/claude-mpm155—~937Automated safety check: PassApache-2.0
Trellis Session Insightmindfold-ai/Trellis15k4 repos~1.7kAutomated safety check: PassAGPL-3.0
Native Data FetchingCherryHQ/cherry-studio-app4k6 repos~2.9kAutomated safety check: NotesMIT
Aoti Debugpytorch/pytorch104k1 repos~1.7kAutomated safety check: PassCustom licence
Herdr Throwaway Reproductionherdrdev/herdr43k—~2.4kAutomated safety check: PassApache-2.0
Systematic Debuggingultralisp/ultralisp25851 repos~2.4kAutomated safety check: PassNone

Similar skills

  • Trellis Session Insight

    mindfold-ai/Trellis

    Reach into past AI conversation history through the trellis mem CLI.

    15k GitHub starsUsed in 4 repos~1.7k tokens
    DevelopmentAuto-check passed
  • Native Data Fetching

    CherryHQ/cherry-studio-app

    A skill your agent uses when implementing or debugging ANY network request, API call, or data fetching.

    4k GitHub starsUsed in 6 repos~2.9k tokens
    DevelopmentAuto-check: notes
  • Aoti Debug

    pytorch/pytorch

    Debug AOTInductor (AOTI) errors and crashes. An agent skill from pytorch/pytorch.

    104k GitHub starsUsed in 1 repo~1.7k tokens
    DevelopmentAuto-check passed
  • Runs a disposable, uniquely named Herdr session inside an existing one so runtime, pane, terminal or API bugs can be reproduced without touching the main session.

    43k GitHub stars~2.4k tokensUpdated today
    DevelopmentAuto-check passed
  • Systematic Debugging

    ultralisp/ultralisp

    A skill your agent uses when encountering any bug, test failure, or unexpected behavior, before proposing fixes

    258 GitHub starsUsed in 51 repos~2.4k tokens
    DevelopmentAuto-check passed
  • Decides whether an OpenLogi device problem on macOS is a privacy-permission (TCC) problem, using agent log lines, and says which identity needs which grant.

    23k GitHub stars~2.5k tokensUpdated 4 days ago
    DevelopmentAuto-check: notes

More from bobmatnyc/claude-mpm

All 63 skills in this repo
  • Build MCP Server

    bobmatnyc/claude-mpm

    Create high-quality MCP servers that enable LLMs to effectively interact with external services.

    155 GitHub stars~2k tokensUpdated 1 mo ago
    Auto-check passed
  • Env Manager

    bobmatnyc/claude-mpm

    Environment variable validation, synchronization, and management across local development, CI/CD, and deployment platforms

    155 GitHub stars~2k tokensUpdated 1 mo ago
    Auto-check: notes
  • Session Analyzer

    bobmatnyc/claude-mpm

    Debug and teach agentic coding: a deterministic-first session timeline + cost report, with optional narrative polish and a standalone JSX visualiser.

    155 GitHub stars~2.2k tokensUpdated 1 mo ago
    Auto-check passed
  • Software Patterns

    bobmatnyc/claude-mpm

    Decision framework for architectural patterns including DI, SOA, Repository, Domain Events, Circuit Breaker, and Anti-Corruption Layer.

    155 GitHub stars~1.8k tokensUpdated 1 mo ago
    Auto-check passed
  • Verification Before Completion

    bobmatnyc/claude-mpm

    Run verification commands and confirm output before claiming success

    155 GitHub starsUsed in 2 repos~1k tokens
    Auto-check passed
  • Dependency Audit

    bobmatnyc/claude-mpm

    Dependency audit and cleanup workflow for maintaining healthy project dependencies.

    155 GitHub stars~3.5k tokensUpdated 1 mo ago
    Auto-check passed

Categories

Questions about Systematic Debugging

What does Systematic Debugging do?

Systematic debugging methodology emphasizing root cause analysis over quick fixes. Systematic Debugging is an agent skill from bobmatnyc/claude-mpm.

When should I use Systematic Debugging?

Systematic Debugging fits situations like: tasks that involve Debugging.

How do I install Systematic Debugging in Claude Code?

Run `npx skills add bobmatnyc/claude-mpm --skill systematic-debugging -a claude-code`. Or copy the skill folder (plugin/skills/universal-debugging-systematic-debugging in bobmatnyc/claude-mpm) into .claude/skills/systematic-debugging in your project. Claude Code loads it when a task matches its description.

How do I install Systematic Debugging in Codex?

Run `npx skills add bobmatnyc/claude-mpm --skill systematic-debugging -a codex`. Or copy the skill folder (plugin/skills/universal-debugging-systematic-debugging in bobmatnyc/claude-mpm) into .agents/skills/systematic-debugging in your project. Codex loads it when a task matches its description.

Can I use Systematic Debugging in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add bobmatnyc/claude-mpm --skill systematic-debugging -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/systematic-debugging, .gemini/skills/systematic-debugging, .github/skills/systematic-debugging and .opencode/skills/systematic-debugging in your project.

What does Systematic Debugging need to run?

SKILL.md names no scripts, command-line tools or credentials: Systematic Debugging is instructions for the agent only. Compatibility (from SKILL.md): claude-code.

Does Systematic Debugging access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Systematic Debugging safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Systematic Debugging use?

Systematic Debugging is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Systematic Debugging use?

About 937 tokens (SKILL.md is roughly 3.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 11k tokens, read only when the agent opens those files.

What are the alternatives to Systematic Debugging?

Skills that share tags, products or a category with Systematic Debugging: Trellis Session Insight (mindfold-ai/Trellis, 15k stars), Native Data Fetching (CherryHQ/cherry-studio-app, 4k stars), Aoti Debug (pytorch/pytorch, 104k stars) and Herdr Throwaway Reproduction (herdrdev/herdr, 43k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Systematic Debugging?

bobmatnyc (a GitHub user) maintains it in bobmatnyc/claude-mpm, which has 155 GitHub stars. The repository holds 63 skills in this directory. The repository was last updated on August 31, 2026.

Source: bobmatnyc/claude-mpm on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.