
Systematic Debugging
Forces you to trace through the actual code and understand why something breaks instead of pattern-matching to fixes you've seen before. When a bug appears, it walks you through reading implementations completely, understanding dependencies, and comparing against references before proposing solutions. The skill explicitly disables quick LLM fixes and pushes back against "I've seen this a hundred times" reasoning. Honestly, this will slow you down initially and might frustrate senior engineers who want to move fast, but it's designed to prevent the cascade of workarounds that happen when you fix symptoms instead of root causes.
- skills.sh installs
- 391
- GitHub stars
- 79
- last updated
- Aug 21, 2026
Install
$ npx -y skills add bobmatnyc/claude-mpm-skills --skill systematic-debugging --agent claude-codeInstalls into .claude/skills of the current project.
Files
Systematic Debugging
When to Use
- A bug, error, exception, or crash needs investigation
- Something is "not working" and the cause is unclear
- A test is failing and the reason isn't obvious
- Unexpected behavior needs troubleshooting in any language or framework
Core Workflow
Follow these five phases sequentially. Do not skip ahead to fixing before completing isolation and tracing.
Phase 1: Reproduce
Establish a reliable way to trigger the bug before doing anything else.
- Read the full error message, stack trace, and logs — note exact text, line numbers, and error codes
- Create a minimal reproduction case that triggers the issue consistently
- Record the exact steps, inputs, and environment that cause the failure
Checkpoint: Can you trigger the bug on demand? If intermittent, gather more data before proceeding.
Phase 2: Isolate
Narrow down where the failure originates.
- Use binary search to find the failing component — disable or stub out halves of the system
- Check recent changes with
git log --oneline -20andgit diffagainst the last known good state - Add targeted logging or use a debugger to observe state at key boundaries
Sponsors
Details
- Repository
- github.com/bobmatnyc/claude-mpm-skills
- Categories
- Frontend Development, Git & Pull Requests, Debugging, Automation & Workflows
- First seen
- Jun 3, 2026
More from bobmatnyc/claude-mpm-skills
All 158- Vue390
- Api Documentation389
- Screenshot389
- Software Patterns382
- Nextjs V16380
- Vercel Deployments Builds378
- Security Scanning377
- Test Quality Inspector376
- Svelte5 Runes Static373
- Stacked Prs371
- Better Auth Core368
- Homebrew Formula Maintenance366
- Better Auth Integrations363
- Reporting Pipelines363
- Better Auth Plugins362
- Git Worktrees360
- Nextjs Core357
- Fastapi Local Dev356
- Vb Winforms356
- Headlessui355
- Jest Typescript354
- Vercel Networking Domains353
- Svelte352
- Sec Edgar Pipeline351