skills.rest
fernandoxavier02
fernandoxavier02COMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

Enforce a four-phase systematic debugging process to identify and resolve root causes.

Updated Aug 23, 2026
Search Tags:#testing#debugging#defense-in-depth#systematic#traceability#phases#root-cause
One-click install
npx skills add https://github.com/fernandoxavier02/Superpower-Gemini --skill systematic-debugging-fernandoxavier02
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/fernandoxavier02/Superpower-Gemini/tree/main/skills/systematic-debugging
Command: npx skills add https://github.com/fernandoxavier02/Superpower-Gemini --skill systematic-debugging-fernandoxavier02

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging prevents time-wasting guesswork by enforcing a four-phase process that ensures root causes are identified before fixes.

Core Features & Use Cases

  • Enforces Phase 1 Root Cause Investigation, Phase 2 Pattern Analysis, Phase 3 Hypothesis and Testing, and Phase 4 Implementation to structure debugging.
  • Provides anti-pattern guidance and defense-in-depth practices to catch edge cases and ensure robust fixes.
  • Applicable to bugs in tests, production, and complex systems, especially under time pressure or with tight deadlines.

Quick Start

Load the skill and follow Phase 1 through Phase 4 to resolve issues.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema
What is the best way to find the root cause of a bug in a complex codebase?▼

Systematic debugging enforces a four-phase process—root-cause investigation, pattern analysis, hypothesis testing, and implementation—to resolve bugs in complex codebases without time-wasting guesswork.

How do I debug production failures systematically under time pressure?▼

To debug production failures under time pressure, follow a structured four-phase debugging process: investigate root causes, analyze patterns, test hypotheses, and implement fixes with anti-pattern avoidance and defense-in-depth notes.

What is a systematic debugging process for resolving unexpected software behavior?▼

Systematic debugging resolves unexpected software behavior by enforcing four phases: root-cause investigation, pattern analysis, hypothesis testing, and implementation, ensuring robust fixes and avoiding anti-patterns.

How do I avoid patchwork fixes when debugging test failures?▼

Avoid patchwork fixes by enforcing a four-phase debugging process that requires documenting root-cause investigation and pattern analysis before implementation, ensuring test failures are resolved at their source.

Does systematic debugging work for both test failures and production bugs?▼

Yes, systematic debugging applies to test failures, production bugs, and unexpected behavior by enforcing a consistent four-phase process: root-cause investigation, pattern analysis, hypothesis testing, and implementation.

Related Skills

Explore More Software Engineering Skills→
derHakenderHaken
437

systematic-debugging

Trace data flow and apply a four-phase process to fix root causes.

Community
Advanced
DYAI2025DYAI2025

regression-test-generator

Generate Arrange-Act-Assert regression tests for Jest, Vitest, pytest, or Playwright.

Community
Intermediate
macaughmacaugh
5

Static Vulnerability Analysis

Detects injection, memory safety and authorization flaws in multiple languages.

Community
Advanced
outfitter-devoutfitter-dev
28

debugging-and-diagnosis

Enforce a four-phase root-cause investigation framework for software debugging.

Official
Advanced