skills.rest
rodrigobranas
rodrigobranasCOMMUNITY
Explore all skills by this author →
Website𝕏@rodrigobranasGitHub

systematic-debugging

Enforce a four-phase root-cause debugging process before implementing fixes.

1|1|Updated Apr 18, 2026
Search Tags:#debugging#investigation#anti-patterns#defense-in-depth#systematic#phases#root-cause
One-click install
npx skills add https://github.com/rodrigobranas/formacao_ia_arq_t1_4 --skill systematic-debugging-rodrigobranas
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/rodrigobranas/formacao_ia_arq_t1_4/tree/main/mastra-rag/.agents/skills/systematic-debugging
Command: npx skills add https://github.com/rodrigobranas/formacao_ia_arq_t1_4 --skill systematic-debugging-rodrigobranas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging provides a disciplined, step-by-step approach to uncover root causes rather than applying symptom fixes, reducing rework and cognitive load during incidents.

Core Features & Use Cases

  • Four-Phase Process: Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, and Implementation, ensuring no phase is skipped.
  • Anti-patterns & Defense-in-Depth: Explicitly documents shortcuts to avoid and recommends layered validation to prevent regression.
  • Use Case: Engineers facing bugs, flaky tests, or production incidents who need reliable root-cause resolution.

Quick Start

Read error messages, reproduce reliably, complete Phase 1 through Phase 4, and only then propose 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 a systematic process help fix bugs?▼

Root-cause debugging enforces a disciplined, four-phase process to uncover true origins of bugs rather than applying symptom fixes, reducing rework and cognitive load during incidents.

How do I debug flaky tests and production incidents without skipping investigation steps?▼

Complete a four-phase debugging process: root cause investigation, pattern analysis, hypothesis and testing, and implementation, ensuring no phase is skipped before proposing fixes.

What debugging anti-patterns should I avoid when investigating unexpected software behavior?▼

Avoid symptom fixes and shortcuts that bypass the structured investigation phases, and instead apply defense-in-depth with layered validation to prevent regression after the fix.

Does systematic debugging work for high-pressure production incidents and unexpected behavior across software projects?▼

Yes, the systematic debugging process applies to bugs, test failures, and unexpected behavior across software projects, including high-pressure production incident scenarios requiring reliable resolution.

What's the best way to structure a debugging workflow from investigation to implementation?▼

Structure debugging through four sequential phases: start with root cause investigation, perform pattern analysis, conduct hypothesis and testing, and finish with implementation before proposing fixes.

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
wineastwineast
1

add-regression-test

Generate regression tests for React components, hooks, and API endpoints.

Community
Intermediate
chadanandachadananda

systematic-debugging

Guide engineers through a four-phase root-cause debugging workflow.

Community
Basic
ilderajilderaj

systematic-debugging

Enforce root-cause investigation before fixes across four debugging phases.

Community
Advanced