bobmatnyc avatar

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-code

Installs 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.

  1. Read the full error message, stack trace, and logs — note exact text, line numbers, and error codes
  2. Create a minimal reproduction case that triggers the issue consistently
  3. 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.

  1. Use binary search to find the failing component — disable or stub out halves of the system
  2. Check recent changes with git log --oneline -20 and git diff against the last known good state
  3. 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
1mims-harvard avatartooluniverse-gene-enrichmentmims-harvard/tooluniverseGene-set enrichment analysis — GO (Biological Process, Molecular Function, Cellular Component), KEGG, Reactome pathway enrichment via clusterProfiler, gseapy, O390skills.sh installs
2gocallum avatarmcp-server-skillsgocallum/nextjs16-agent-skillsPattern for building MCP servers in Next.js with mcp-handler, shared Zod schemas, and reusable server actions.387skills.sh installs
3levnikolaevich avatarln-742-precommit-setuplevnikolaevich/claude-code-skillsConfigures Husky, lint-staged, commitlint, and Python pre-commit hooks. Use when adding Git hook automation to a project.385skills.sh installs
4davila7 avatartheme-factorydavila7/claude-code-templatesToolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors/fo384skills.sh installs
5secondsky avatarwoocommerce-backend-devsecondsky/claude-skillsAdd or modify WooCommerce backend PHP code following project conventions. Use when creating new classes, methods, hooks, or modifying existing backend code in W379skills.sh installs
6levnikolaevich avatarln-646-project-structure-auditorlevnikolaevich/claude-code-skillsAudits physical architecture structure: modules, domains, layer layout, junk drawers, and framework placement. Use for structure drift.376skills.sh installs