skills.rest
nicolas-deyros
nicolas-deyrosCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

systematic-debugging

Enforce a four-phase workflow for root-cause debugging of bugs and test failures.

Updated Jul 15, 2025
Search Tags:#testing#defense-in-depth#tracing#root-cause#phase-management#systematic-debugging#debugging-process
One-click install
npx skills add https://github.com/nicolas-deyros/astro-portfolio-v2 --skill systematic-debugging-nicolas-deyros
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/nicolas-deyros/astro-portfolio-v2/tree/main/.agents/skills/systematic-debugging
Command: npx skills add https://github.com/nicolas-deyros/astro-portfolio-v2 --skill systematic-debugging-nicolas-deyros

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic Debugging guides engineers to identify root causes of bugs and flaky tests before proposing fixes, reducing wasted time on symptom fixes.

Core Features & Use Cases

  • Phase-driven investigation: Phase 1 Root Cause Investigation, Phase 2 Pattern Analysis, Phase 3 Hypothesis and Testing, Phase 4 Implementation.
  • Anti-pattern awareness: Red flags and defense-in-depth recommendations to avoid quick fixes.
  • Real-world applicability: Used for production bugs, flaky tests, and deep-stack issues.

Quick Start

To begin, load the skill with skills/debugging/systematic-debugging and follow Phase 1 Root Cause Investigation before attempting any fixes.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema
What is a systematic debugging process for finding root causes?▼

A systematic debugging process enforces a four-phase workflow—root cause investigation, pattern analysis, hypothesis testing, and implementation—to resolve bugs and test failures before applying fixes.

How do I debug flaky tests and production bugs without fixing symptoms?▼

Debug flaky tests and production bugs by completing a full root cause investigation first, analyzing behavioral patterns, and testing hypotheses before implementation to ensure durable resolutions.

What's the best way to structure root-cause debugging for complex software issues?▼

The best way to structure root-cause debugging is using a phase-driven analysis workflow that requires complete Phase 1 investigation, pattern analysis, and hypothesis testing before implementing any code fixes.

When should I use defense-in-depth and tracing during the debugging workflow?▼

Use defense-in-depth and tracing during the debugging workflow to identify anti-patterns and red flags, ensuring repeatable investigations across deep-stack issues and behavioral anomalies before fixes.

Can I apply systematic debugging to behavioral anomalies in production environments?▼

Yes, you can apply systematic debugging to behavioral anomalies in production environments, as the four-phase workflow handles production bugs, test flakiness, and deep-stack issues for repeatable investigations.

Why does fixing symptoms instead of root causes lead to recurring test failures?▼

Fixing symptoms leads to recurring test failures because quick fixes bypass the required root cause investigation, pattern analysis, and hypothesis testing phases needed to guarantee durable resolutions.

Related Skills

Explore More Software Engineering Skills→
allexcdallexcd

autonomous-bug-fixing

Diagnose, reproduce, and fix code defects from bug reports or error logs.

Community
Advanced
aist-ai-sastaist-ai-sast

mcp-regression-fix

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

Official
Advanced
lv7devlv7dev

Root Cause Tracing

Trace call stacks backward to identify original bug triggers.

Community
Advanced
slantviewslantview
1

error-detective

Correlate error patterns and stack traces across logs and codebases.

Community
Intermediate