skills.rest
dazuck
dazuckCOMMUNITY
Explore all skills by this author →
Website𝕏@dazuckGitHub

systematic-debugging

Guide bug fixes through symptom gathering, reproduction, isolation, and hypothesis testing.

1|Updated Jan 11, 2026
Search Tags:#debugging#documentation#isolation#systematic#reproduction#test-first#hypothesis-testing
One-click install
npx skills add https://github.com/dazuck/claude-code-skills --skill systematic-debugging-dazuck
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/dazuck/claude-code-skills/tree/main/skills/systematic-debugging
Command: npx skills add https://github.com/dazuck/claude-code-skills --skill systematic-debugging-dazuck

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a disciplined debugging framework that guides you from symptom capture to a minimal, test-first fix, reducing guesswork and accelerating learning.

Core Features & Use Cases

  • Reproducible debugging workflow: Gather symptoms, reproduce reliably, isolate the failing path.
  • Hypothesis-driven debugging: Form theories and validate with tests before touching code.
  • Documentation and learning: Capture learnings and prevent regressions with a structured format.

Use Cases:

  • When a bug stalls your sprint, apply this framework to reproduce and fix quickly.
  • During code reviews to standardize debugging practices.

Quick Start

To begin, invoke systematic-debugging on a failing component, start by collecting symptoms, then reproduce and isolate. Then form a hypothesis, write a failing test, implement a minimal fix, run the full suite, and document learnings.

Frequently Asked Questions about systematic-debugging

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is a systematic debugging framework and when do I need it?▼

Hypothesis-driven debugging means forming theories about a bug and validating them with failing tests before touching code. It differs by enforcing test-first fixes and structured documentation, preventing regressions instead of relying on trial-and-error code changes.

How do I debug a failing component step by step?▼

To debug systematically, collect symptoms, reproduce the issue reliably, and isolate the failing path. Then form a hypothesis, write a failing test, implement a minimal fix, run the full test suite, and document learnings to prevent future regressions.

Does systematic debugging work for team code reviews or just solo development?▼

Systematic debugging works across development teams for both solo work and code reviews. It standardizes debugging practices by enforcing a structured format for symptom gathering, hypothesis testing, minimal fixes, and regression prevention that the whole team can follow.

Why should I write a failing test before implementing a bug fix?▼

Writing a failing test before fixing ensures your hypothesis is validated and the bug is reliably reproduced. It enforces a test-first workflow that confirms the minimal fix resolves the isolated issue and prevents regressions across the full test suite.

Related Skills

Explore More Software Engineering Skills→
hollandkevinthollandkevint
5

debug

Reproduce software issues and analyze root causes systematically.

Community
Intermediate
FlorinSenonerFlorinSenoner

fix-tests

Resolve failing Playwright end-to-end tests with minimal fixes and full suite regression checks.

Community
Advanced
korchasakorchasa
3

flow-skill-fix-tests

Diagnoses and fixes failing tests through a guided, step-by-step workflow.

Community
Intermediate
potenlabpotenlab
2

quick

Apply minimal validated patches for small UI, typo, and documentation edits.

Community
Basic