systematic-debugging

Guide root-cause investigation across four phases before implementing fixes.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Scripsteam/scrips-stack --skill systematic-debugging-scripsteam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/Scripsteam/scrips-stack/tree/main/methodology/systematic-debugging
Command: npx skills add https://github.com/Scripsteam/scrips-stack --skill systematic-debugging-scripsteam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic Debugging provides a disciplined, phase-based approach to diagnose root causes before attempting fixes. It prevents random patches and accelerates durable resolutions by guiding you through structured data collection, evidence gathering, and hypothesis testing.

Core Features & Use Cases

  • Phase 1: Root Cause Investigation — read error messages carefully, reproduce consistently, review recent changes, and collect diagnostic data.
  • Phase 2: Pattern Analysis — find working references, compare against references, identify differences, and understand dependencies.
  • Phase 3: Hypothesis and Testing — form a single hypothesis, test minimally, verify before continuing, and escalate if needed.
  • Phase 4: Implementation — create a failing test case, implement the root fix, and verify the solution with guardrails to prevent regression.
  • Supporting Techniques & Real-World Impact — trace data flow, validate across components, and reduce time-to-resolution through disciplined workflows.

Quick Start

Initiate Phase 1 by reproducing the issue, capturing error messages, and collecting diagnostic evidence to identify the root cause.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema
How do I find the root cause of a bug instead of guessing fixes?

To find the root cause of a bug, follow a four-phase discipline: investigate root causes by reproducing the issue, analyze patterns against working references, test a single hypothesis minimally, and implement the fix with a failing test case.

What is the best way to debug production issues across multi-component systems?

The best way to debug production issues across multi-component systems is to trace data flow, validate components, and collect diagnostic evidence through a structured root cause investigation before attempting any fixes.

How do I reproduce test failures consistently to start debugging?

To reproduce test failures consistently, start Phase 1 by reading error messages carefully, capturing diagnostic data, and reviewing recent changes to understand the exact conditions triggering the failure.

How do you test a debugging hypothesis before applying a fix?

To test a debugging hypothesis before applying a fix, form a single hypothesis during Phase 3, test it minimally, verify the results, and escalate if the hypothesis does not resolve the issue.

Does systematic debugging work for performance anomalies and not just code errors?

Systematic debugging works for performance anomalies by applying the same four-phase discipline: collecting diagnostic evidence, analyzing patterns, testing a single hypothesis, and implementing a verified root fix.

Why should I create a failing test case when fixing a bug?

You should create a failing test case during Phase 4 to verify the bug exists, implement the root fix, and establish guardrails that confirm the solution and prevent future regression.