skills.rest
zephyrflow97
zephyrflow97COMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

Trains engineers to root-cause analyze before proposing fixes in four phases.

Updated Aug 23, 2026
Search Tags:#workflow#debugging#validation#defense-in-depth#root-cause#data-flow#phase
One-click install
npx skills add https://github.com/zephyrflow97/cadence --skill systematic-debugging-zephyrflow97
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/zephyrflow97/cadence/tree/main/skills/systematic-debugging
Command: npx skills add https://github.com/zephyrflow97/cadence --skill systematic-debugging-zephyrflow97

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides engineers to perform a rigorous root-cause investigation before proposing fixes, eliminating symptom-driven patches and reducing wasted debugging time.

Core Features & Use Cases

  • Four-phase debugging workflow: Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, Implementation.
  • Defense-in-depth: validates data flow and adds multiple validation layers to prevent regression.
  • Cross-scenario applicability: useful for code bugs, flaky tests, production incidents, and complex architectures.
  • Comprehensive references: links to trace techniques, anti-patterns, and testing approaches.

Quick Start

Load the skill and follow the Phase 1 checklist to begin with 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 root-cause debugging and how does it stop symptom-driven patches?▼

Root-cause debugging enforces a rigorous investigation of data flow and defect origins before proposing fixes. It prevents superficial patches by tracing complex bug cascades to their actual source, ensuring the underlying issue is resolved rather than just masking symptoms.

How do I debug flaky tests and production incidents systematically?▼

Debug flaky tests and production incidents by following a four-phase workflow: Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, and Implementation. This structured approach traces data flow and validates hypotheses before applying code fixes.

What is the best way to trace data flow in complex bug cascades?▼

Tracing data flow in complex bug cascades requires a systematic pattern analysis phase. By mapping how data moves through affected systems and applying layered defenses, engineers can identify root causes across code defects and architecture interactions.

Does this debugging workflow apply to code defects in complex architectures?▼

Yes, this debugging workflow applies directly to code defects in complex architectures. It uses cross-scenario applicability to handle production incidents and bug cascades by validating data flow across multiple system layers.

How do I prevent regression when fixing a bug?▼

Prevent regression by applying defense-in-depth during the implementation phase. This approach adds multiple validation layers to verify data flow and ensures fixes are robust against future edge cases and bug reintroductions.

Related Skills

Explore More Software Engineering Skills→
rbah31rbah31
5

runbook

Investigate production symptoms and generate structured incident reports from logs, metrics, and traces.

Community
Intermediate
mazicimertmazicimert

tdd-bug-fix

Reproduce bugs with failing tests and guide a minimal TDD fix workflow.

Community
Advanced
mwaymway
4

systematic-debugging

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

Community
Advanced
cq112233cq112233
21

systematic-debugging

Diagnose technical bugs through a four-phase root cause investigation framework.

Community
Advanced