skills.rest
Shade666
Shade666COMMUNITY
Explore all skills by this author →
GitHub

Radberi-SystematicDebugging

Guide structured root-cause investigation through four phases before implementing fixes.

1|Updated Mar 20, 2026
Search Tags:#debugging#anti-patterns#defense-in-depth#systematic#phases#root-cause
One-click install
npx skills add https://github.com/Shade666/huml-dotnet --skill radberi-systematicdebugging
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Radberi-SystematicDebugging
Source: https://github.com/Shade666/huml-dotnet/tree/main/.claude/skills/Radberi-SystematicDebugging
Command: npx skills add https://github.com/Shade666/huml-dotnet --skill radberi-systematicdebugging

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a disciplined approach to debugging that ensures root-cause investigation is completed before proposing fixes, preventing symptom-driven patches and time-wasting cycles. It reinforces a core principle: ALWAYS find root cause before attempting fixes.

Core Features & Use Cases

  • Four-phase workflow (Root Cause Investigation → Pattern Analysis → Hypothesis & Testing → Implementation) with a mandatory Phase 1 before any fixes.
  • Anti-patterns and explicit language defenses to resist time-pressure shortcuts and ensure thorough investigation.
  • Defense-in-depth and supportive artifacts (root-cause tracing, validation patterns) to prevent regressions and surface the true origin of issues.
  • Related skills and references: Radberi-TDD and Radberi-VerificationBeforeCompletion for testing discipline.

Quick Start

Load the Radberi-SystematicDebugging skill and follow Phase 1 before proposing any fixes.

Frequently Asked Questions about Radberi-SystematicDebugging

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

FAQPage Schema
What is systematic debugging and how does it prevent symptom fixes?▼

Systematic debugging enforces a mandatory root-cause investigation phase before fixes, preventing symptom-driven patches by requiring evidence documentation and pattern analysis to identify the true origin of software issues.

How do I find the root cause of test failures and production issues?▼

To find the root cause of test failures, follow a structured four-phase workflow: investigate root causes, analyze patterns, test hypotheses, and only then implement fixes, ensuring thorough evidence collection before modifying code.

What is the best way to stop applying patches that only fix symptoms?▼

The best way to stop symptom patches is to enforce a strict root-cause investigation phase with explicit anti-patterns, preventing shortcuts under time pressure and requiring documented validation patterns before any code changes.

Does systematic debugging work with test-driven development workflows?▼

Yes, systematic debugging integrates with test-driven development workflows by referencing related skills like Radberi-TDD and Radberi-VerificationBeforeCompletion to maintain testing discipline and prevent regressions during the implementation phase.

What are common debugging anti-patterns to avoid under time pressure?▼

Common debugging anti-patterns include skipping the root-cause investigation phase, applying immediate symptom fixes, and ignoring defense-in-depth validation, all of which lead to time-wasting regression cycles and unresolved underlying issues.

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
sswapnil2sswapnil2

systematic-debugging

Enforce a four-phase trace-back debugging process to identify root causes before fixes.

Community
Advanced
tmalcolm-0607tmalcolm-0607

mad-implement

Enforce TDD workflows and quality gates across .NET and Node.js implementation phases.

Community
Advanced
paopp2paopp2

Systematic Debugging

Enforces a four-phase workflow for root-cause analysis of software issues before fixes are allowed.

Community
Basic