Skip to main content
skill CX Codex

systematic-debugging · chriswiles — Claude Code skill: guide and install

systematic-debugging enforces a four-phase troubleshooting protocol rooted in root cause analysis. Ideal for tracking down broken test suites or runtime errors without trial-and-error edits.

no license ★ 6,091 updated 2026-01-06

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add ChrisWiles/claude-code-showcase --skill systematic-debugging -a claude-code
Open on GitHub

What systematic-debugging does

The skill prevents touching production code before uncovering the true source of an error. Instead of patching visible symptoms, the agent inspects the entire stack trace, traces faulty inputs backward up the execution stack, and establishes reproducible steps. The workflow progresses through four clear stages: finding the root cause, comparing against working code, testing a single hypothesis, and creating a targeted fix.

A failing reproduction test must exist before changing code. This prevents guesswork. If three consecutive fixes fail, the workflow demands an immediate halt: repeated failures indicate architectural issues that require rethinking the design instead of adding more patches.

Specific walkthroughs cover test assertion failures, runtime exceptions, regressions diagnosed with git bisect, and race conditions. The guide also integrates with the testing-patterns skill.

What it helps with

  • isolate the upstream origin of invalid data
  • eliminate haphazard trial-and-error code edits
  • write a reproducible failing test before patching
  • debug intermittent race conditions and timing issues

Example prompts for the agent

  • Inspect the stack trace in auth.service.ts and locate the root cause following systematic-debugging
  • The suite in order.spec.ts failed: form a single hypothesis and write a reproduction test before fixing anything

How to install systematic-debugging

1Skills CLI (Vercel)

npx skills add ChrisWiles/claude-code-showcase --skill systematic-debugging -a claude-code

2Manually: put the files in place

~/.claude/skills/systematic-debugging/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/systematic-debugging/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about systematic-debugging

How to install systematic-debugging in Claude Code?

Run npx skills add ChrisWiles/claude-code-showcase --skill systematic-debugging -a claude-code in your terminal.

What does systematic-debugging do?

It directs Claude Code through a strict troubleshooting process. The agent uncovers the underlying trigger and tests assumptions rather than generating superficial fixes.

What happens if three fixes fail in a row?

The protocol commands an immediate stop. Three consecutive failed attempts indicate an architectural flaw that needs redesign discussion instead of further patching.

Similar skills

All skills for Testing and QA →

systematic-debugging by other authors comes first.

systematic-debugging Jesse Vincent systematic-debugging is a Claude Code and Codex skill that blocks fixes until root cause analysis is complete. It activates on test failures, bugs, or unexpected behavior. CX Codex +1 306,118installs systematic-debugging spencerpauly systematic-debugging enforces a structured debugging workflow on your AI assistant instead of random edits. It helps isolate elusive bugs and verify root causes with evidence. CX Codex +1 604installs systematic-debugging bobmatnyc The systematic-debugging skill guides an agent from reproducing a bug to checking the fix. Use it when an error or unexpected behavior has no clear cause. CX Codex +1 400installs systematic-debugging GanyuanRan The systematic-debugging skill guides bug and test-failure investigations before code changes. Use it to trace a symptom to the logic that owns the cause. CX Codex +1 ★ 1,450repo stars systematic-debugging vstorm-co systematic-debugging walks the agent through five debugging steps, from reproducing the failure to confirming the fix. Useful once random edits stop working. CX Codex +1 ★ 1,125repo stars debugging-and-error-recovery addyosmani The debugging-and-error-recovery Claude Code skill traces failures to their root cause and checks the fix. It activates for failing tests, broken builds, unexpected errors, or behavior that no longer matches expectations. CX Codex +1 79,600installs debug-systematic travisjneuman debug-systematic — a four-phase debugging skill for hard-to-reproduce failures, race conditions, and unexplained behavior. It guides the agent from reproduction to verified fix. CX Codex +1 152installs service-debugging c0x12c service-debugging is a Claude Code skill for investigating backend failures, from gathering symptoms and inspecting logs to isolating root causes with git bisect. CX Codex +1 ★ 111repo stars debugging mrgoonie Enforces a disciplined debugging methodology that stops guesswork and requires fresh test proof before marking tasks done. CX Codex +1 580installs debugging-toolkit-debugger Seth Hobson The debugging-toolkit-debugger subagent investigates errors, failed tests, and odd behavior by tracing failures to their cause and checking a focused fix. CX Codex ★ 42,780repo stars laravel-systematic-debugging iSerter The laravel-systematic-debugging skill guides an agent through investigating Laravel errors before changing code. Use it for failing tests, Eloquent issues, and unexpected application behavior. CX Codex +1 110installs

From the same set11

The whole set →
pr-review pr-review inspects pull requests through the GitHub CLI against project standards and posts tiered review notes. CX Codex +1 ★ 6,091repo stars code-quality code-quality reviews TypeScript files in a chosen directory, runs npm checks, and groups findings by severity. Use it before a code change or review. CX Codex +1 ★ 6,091repo stars docs-sync docs-sync is a Claude Code command that compares documentation with recent code changes and flags inconsistencies. It catches outdated examples, incorrect API signatures, and mismatched parameter types. CX Codex +1 ★ 6,091repo stars github-workflow github-workflow manages Git branches, Conventional Commits, and pull requests according to team conventions. Helpful for keeping repository history structured and tidy. CX Codex ★ 6,091repo stars ticket Handles the full ticket workflow: fetch task details from JIRA or Linear, explore related code, implement changes, and create a linked PR. Reduces manual sync between issue tracker and repository. CX Codex +1 ★ 6,091repo stars code-reviewer code-reviewer — a subagent for Claude Code that checks newly written or modified code against project standards, TypeScript strict mode, and security patterns. CX Codex ★ 6,091repo stars graphql-schema The graphql-schema skill sets conventions for GraphQL queries, mutations, and type generation. It fits projects that use Apollo Client. CX Codex +1 ★ 6,091repo stars formik-patterns formik-patterns adds Formik form recipes to Claude: Yup schemas, field handlers, a submit flow and multi-step forms. CX Codex +1 ★ 6,091repo stars

Project sponsors

Companies that keep this analytics open