Systematic Debugging

Systematic Debugging is a Quality skill for Claude Code, published by vstorm-co in pydantic-deepagents.

1K stars126 forkson vstorm-co/pydantic-deepagentsAdded 2026/08/21Repository updated 2026/08/20

agent-frameworkai-agentsanthropicclaude-codeclicoding-agentdeep-researchdocker-sandboxllmsmcpplaywrightpydanticpydantic-aipythonsubagentstuivstorm

Install in seconds

Install Systematic Debugging

Copy Systematic Debugging into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.

terminal

npx degit https://github.com/vstorm-co/pydantic-deepagents/tree/main/pydantic_deep/bundled_skills/systematic-debugging ~/.claude/skills/systematic-debugging

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/vstorm-co/pydantic-deepagents.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file: pydantic_deep/bundled_skills/systematic-debugging/SKILL.md in vstorm-co/pydantic-deepagents
Installs to: ~/.claude/skills/systematic-debugging
Collection: One of 14 skills cataloged from this repository
Category: Quality — 1354 skills

What Systematic Debugging does

Systematic Debugging provides a step-by-step loop to reproduce, isolate, diagnose, fix, and verify bugs. Use it when code fails, gives wrong output, times out, or behaves differently across environments.

Systematic Debugging is cataloged under Quality on DirSkills. Systematic Debugging comes from a repository tagged agent-framework, ai-agents, anthropic, claude-code and cli.

Documentation

README

Excerpt

Systematic Debugging

A structured approach to finding and fixing bugs.

The Debugging Loop

1. REPRODUCE → 2. ISOLATE → 3. DIAGNOSE → 4. FIX → 5. VERIFY

Never skip steps. Never guess-and-check repeatedly.

Step 1: Reproduce

Run the exact command that fails
Capture FULL output (stdout AND stderr)
Note: exit code, error message, stack trace
If intermittent, identify what changes between runs

Step 2: Isolate

What's the MINIMAL input that triggers the error?
Which specific line/function fails? (read the traceback bottom-up)
Is it a compile error, runtime error, or wrong output?
Does it fail on all inputs or specific ones?

Step 3: Diagnose

Read the error message carefully

This is the opening of the README. Read the full README on GitHub.

Frequently asked about Systematic Debugging

What else does vstorm-co publish alongside Systematic Debugging?
Systematic Debugging is one of 14 skills that DirSkills catalogs from vstorm-co/pydantic-deepagents, the repository it ships in. Its siblings there include Build And Compile, Code Review and Code Review. Each one is a separate skill with its own page in this directory, installs the same way Systematic Debugging does, and is maintained by vstorm-co in that same repository. The rest of the collection is listed on the vstorm-co/pydantic-deepagents page.
How does Systematic Debugging compare to other Quality skills?
Systematic Debugging ranks #825 by stars among the 1354 Quality skills in this catalog. The most-starred ones next to it are Benchmark, Benchmark Optimization Loop and API Design Patterns. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Systematic Debugging against them. Open each page to compare what they document and how they install.