skills.rest
rkz91
rkz91COMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

Guide four-phase root cause investigation before proposing bug fixes.

264|11|Updated Apr 25, 2026
Search Tags:#testing#debugging#defense-in-depth#systematic#root-cause#phase-based#data-tracing
One-click install
npx skills add https://github.com/rkz91/coco --skill systematic-debugging-rkz91
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/rkz91/coco/tree/main/skills/systematic-debugging
Command: npx skills add https://github.com/rkz91/coco --skill systematic-debugging-rkz91

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging provides a disciplined four-phase framework to uncover root causes and avoid symptom fixes, improving speed and reliability in debugging sessions.

Core Features & Use Cases

  • Four-Phase Process: Phase 1 Root Cause Investigation, Phase 2 Pattern Analysis, Phase 3 Hypothesis & Testing, Phase 4 Implementation.
  • Discipline under pressure: Resists quick-fix tendencies and ensures traceability, validation, and defense-in-depth.
  • Use Case: For any bug, test failure, or unexpected behavior across software projects, including production incidents.

Quick Start

Describe the issue and immediately begin with Phase 1: Root Cause Investigation 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 the root cause of a bug instead of just fixing symptoms?▼

Systematic debugging resolves production outages and unexpected behaviors by tracing data-flow and analyzing patterns to identify the root cause. It resists quick-fix tendencies under pressure, ensuring traceability and validation before moving to implementation.

How do I systematically debug a flaky test or production outage?▼

Systematic debugging resolves production outages and unexpected behaviors by tracing data-flow and analyzing patterns to identify the root cause. It resists quick-fix tendencies under pressure, ensuring traceability and validation before moving to implementation.

How do I start a systematic debugging session when a test fails?▼

Begin by describing the issue and immediately entering Phase 1: Root Cause Investigation. You must complete this investigation phase before proposing any fixes, ensuring you isolate the true origin of the test failure through data-flow tracing.

Does this systematic debugging approach apply to any software project or tech stack?▼

Yes, this debugging framework applies to any bug, test failure, or unexpected behavior across all software projects. It operates independently of specific dependencies, using a phase-based process to guide root-cause isolation universally.

Why should I use a phase-based debugging process instead of trying quick fixes?▼

A phase-based debugging process enforces discipline under pressure by requiring pattern analysis and hypothesis testing before implementation. This defense-in-depth approach ensures traceability and validation, significantly reducing the rework caused by quick-fix tendencies.

Related Skills

Explore More Software Engineering Skills→
lgbarnlgbarn
66

shipyard-debugging

Diagnose bugs through root-cause investigation before proposing fixes.

Community
Basic
nashirabbashnashirabbash

systematic-debugging

Trace, analyze, and resolve bugs through a four-phase systematic debugging workflow.

Community
Advanced
timurgaleevtimurgaleev
5

investigate

Guide structured root-cause debugging through phases for context, analysis, hypothesis, and verification.

Community
Advanced
getspurgetspur
2

spurpower-systematic-debugging

Enforce a four-phase investigation workflow for technical issues and software defects.

Official
Advanced