systematic-debugging

Name: systematic-debugging
Availability: InStock
Author: xiaobin

Identifies and fixes bugs by tracing root causes across multi-component systems.

1|Updated Apr 22, 2026

Search Tags:#testing #debugging #defense-in-depth #tracing #root-cause #phase-based

Ready to run

npx skills add https://github.com/xiaobin/superpowers-kimi --skill systematic-debugging-xiaobin

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/xiaobin/superpowers-kimi/tree/main/.agents/skills/systematic-debugging
Command: npx skills add https://github.com/xiaobin/superpowers-kimi --skill systematic-debugging-xiaobin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Systematic Debugging enforces a disciplined, four-phase approach to diagnosing and solving software issues by prioritizing root-cause investigation over quick fixes, reducing wasted time and recurring bugs.

Core Features & Use Cases

Phase 1: Root Cause Investigation to reproduce and gather evidence
Phase 2: Pattern Analysis to compare against references and identify differences
Phase 3: Hypothesis and Testing to form and test minimal changes
Phase 4: Implementation to fix the root cause and verify with tests
Red Flags and anti-patterns to avoid rushed patches

Quick Start

Follow Phase 1 through Phase 4 in order, validating root cause before implementing any fix.

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 flaky test failures before applying a patch?▼

To find the root cause of flaky test failures, reproduce the issue and gather evidence through Phase 1 investigation, then compare patterns against references in Phase 2 to identify differences before forming testable hypotheses. This prevents rushed patches and recurring bugs.

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 using a phased approach: investigate root causes, analyze patterns, test minimal hypotheses, and implement fixes with cross-layer validation. This ensures robust resolution rather than quick temporary patches.

Why do my bug fixes keep recurring after applying patches?▼

Bug fixes recur because patches often address symptoms without tracing root causes. Systematic debugging prevents this by enforcing explicit root-cause investigation and cross-layer validation before implementing any fix, ensuring the actual underlying issue is resolved.

How do I systematically fix bugs in multi-component software systems?▼

Systematically fix bugs by following four phases: gather evidence to reproduce the issue, analyze patterns against references, form and test minimal hypotheses, then implement the root-cause fix and verify with tests. Cross-layer validation ensures robust resolution.

When should I avoid quick patches during software debugging?▼

Avoid quick patches when dealing with test failures, production issues, or flaky behavior across multi-component systems. Instead, enforce explicit root-cause investigation first, as rushed patches waste time and often cause recurring bugs without resolving the underlying problem.

Can I use systematic debugging for both test failures and production issues?▼

Yes, systematic debugging is applicable to test failures, production issues, and flaky behavior across multi-component systems. It enforces root-cause investigation, cross-layer validation, and phased implementation to ensure robust fixes regardless of the environment.