skills.rest
pynbj1001
pynbj1001COMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

Investigate root causes through a four-phase debugging process before proposing fixes.

4|1|Updated Mar 25, 2026
Search Tags:#debugging#traceability#quality-assurance#reproducibility#root-cause#software-engineering#phase-based
One-click install
npx skills add https://github.com/pynbj1001/alpha-sense --skill systematic-debugging-pynbj1001
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/pynbj1001/alpha-sense/tree/main/skills/15.%20superpowers/skills/systematic-debugging
Command: npx skills add https://github.com/pynbj1001/alpha-sense --skill systematic-debugging-pynbj1001

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debugging often devolves into guessing and patching without understanding the underlying cause, leading to recurring issues and wasted time.

Core Features & Use Cases

  • Systematic root-cause investigation: forces you to read error messages, reproduce failures, and trace data flow.
  • Structured analysis: phase-based approach (Root Cause Investigation, Pattern Analysis, Hypothesis Testing, Implementation) to validate fixes.
  • Reproducibility and safety: creates evidence and guardrails to prevent regression.

Quick Start

When you encounter a bug or unexpected behavior, start with Phase 1: Root Cause Investigation by reading errors, reproducing the issue, and tracing data flow before proposing any fixes.

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 a software bug's root cause before attempting a fix?▼

Systematic debugging uses a four-phase process including Root Cause Investigation and Hypothesis Testing to validate fixes. This approach creates evidence and explicit checks, ensuring your code changes are grounded in verified data rather than trial and error.

How do I systematically debug test failures in my CI pipeline?▼

You can systematically debug test failures by reproducing the issue and tracing data flow during the Root Cause Investigation phase. This process applies across development, CI, and production environments to ensure fixes are validated through structured pattern analysis.

Why does my software bug keep recurring after I apply a patch?▼

Your software bug keeps recurring because patching without understanding the underlying cause leads to incomplete fixes. By using a phase-based approach with explicit checks and traceability, you ensure changes are grounded in evidence and prevent future regressions.

Can I use this systematic debugging approach for unexpected behavior in production environments?▼

Yes, this systematic debugging approach is applicable to any bug or unexpected behavior in production environments. It requires a disciplined four-phase process to ensure fixes are validated through hypothesis testing and evidence-based traceability.

Related Skills

Explore More Software Engineering Skills→
mwaymway
4

systematic-debugging

Identify root causes of bugs and test failures through a four-phase debugging workflow.

Community
Advanced
tomguntomgun

fixing-bugs

Reproduce bugs with regression tests and apply minimal root-cause fixes.

Community
Intermediate
EmaRimoldiEmaRimoldi

paper-quality-check

Audit research papers across eight quality dimensions and generate a structured report.

Community
Advanced
dogekikidogekiki

systematic-debugging

Apply a four-phase framework to identify and resolve root causes of technical issues.

Community
Advanced