skills.rest
PlazaCC
PlazaCCOFFICIAL
Explore all skills by this author →
WebsiteGitHub

systematic-debugging

Enforce root-cause investigation before fixes in a four-phase debugging workflow.

2|Updated Apr 11, 2026
Search Tags:#testing#debugging#defense-in-depth#systematic#phases#hypothesis#root-cause
One-click install
npx skills add https://github.com/PlazaCC/antes-da-tela --skill systematic-debugging-plazacc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/PlazaCC/antes-da-tela/tree/main/.agents/skills/systematic-debugging
Command: npx skills add https://github.com/PlazaCC/antes-da-tela --skill systematic-debugging-plazacc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging guides teams to identify root causes before applying fixes, reducing time wasted on symptom patches.

Core Features & Use Cases

  • Four-phase workflow: Root Cause Investigation, Pattern Analysis, Hypothesis and Testing, and Implementation.
  • Anti-patterns, defense-in-depth, and stack-trace techniques to prevent regression.
  • Applicable to bugs, test failures, production incidents, and flaky behavior across codebases.
  • Clear usage patterns and guardrails to improve debugging discipline and outcomes.

Quick Start

Follow the four-phase process by identifying the symptom, reproducing the issue, and completing Phase 1 before proposing any fix.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema
How do I find the root cause of a bug instead of just patching symptoms?▼

To diagnose flaky behavior, apply the systematic debugging workflow: investigate root causes, analyze patterns, test hypotheses, and implement fixes. The process integrates defense-in-depth and stack-trace techniques to prevent regression across codebases.

What is the best way to debug flaky tests and production incidents?▼

The best way to debug flaky tests and production incidents is to apply a systematic debugging workflow that mandates root-cause investigation before fixes. It uses pattern analysis and hypothesis testing to eliminate recurring failures.

How do I stop regression when fixing software bugs?▼

To stop regression when fixing software bugs, integrate defense-in-depth, anti-pattern identification, and stack-trace techniques during the implementation phase. This ensures your hypothesis testing validates the root-cause fix comprehensively.

Does systematic debugging work for both build failures and runtime bugs?▼

Systematic debugging works for build failures, runtime bugs, test failures, and production incidents. Its four-phase workflow enforces root-cause investigation across all software development and QA scenarios before applying any fixes.

When should I not use a root-cause debugging approach?▼

You should not use root-cause debugging when a fast symptom patch is required for immediate production recovery. However, you must still complete the root-cause investigation phase afterward to prevent recurring regressions and identify anti-patterns.

Related Skills

Explore More Software Engineering Skills→
isymchychisymchych

root-cause-analysis

Identify the deepest controllable root cause of a failure with evidence.

Community
Advanced
aist-ai-sastaist-ai-sast

mcp-regression-fix

Diagnose MCP regression failures and implement durable fixes across test suites.

Official
Advanced
wahabmalikwahabmalik

bmad-testarch-ci

Automates CI/CD pipeline setup with test execution and flaky detection via burn-in loops.

Community
Advanced
brenordvbrenordv

linux-troubleshooting

Diagnose Linux system performance, service failures, and network issues.

Community
Intermediate