skills.rest
JaimeJunr
JaimeJunrCOMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

Identify root causes before applying fixes using a four-phase debugging process.

2|Updated Apr 11, 2026
Search Tags:#debugging#defense-in-depth#root-cause#flow-analysis#phase-based#traceback
One-click install
npx skills add https://github.com/JaimeJunr/context-mode --skill systematic-debugging-jaimejunr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/JaimeJunr/context-mode/tree/main/.claude/skills/systematic-debugging
Command: npx skills add https://github.com/JaimeJunr/context-mode --skill systematic-debugging-jaimejunr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic Debugging provides a disciplined framework to identify root causes of bugs, failures, or unexpected behavior before proposing fixes, reducing wasted effort and regressive changes.

Core Features & Use Cases

  • Phase-based workflow: Phase 1 Root Cause Investigation, Phase 2 Pattern Analysis, Phase 3 Hypothesis & Testing, Phase 4 Implementation.
  • Anti-patterns and red flags: explicit STOP rules when shortcuts are attempted, ensuring robust learning and auditability.
  • Defense-in-depth guidance: trace data flow and add validations across multiple layers to prevent regression and surface root causes.

Quick Start

Load the skill and start Phase 1: 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 when should I use it instead of applying quick fixes?▼

Root-cause debugging is a disciplined framework to identify the source of bugs before proposing fixes. Use it to reduce wasted effort and prevent regressive changes when facing production bugs, integration failures, or unexpected behavior.

How do I identify root causes of production bugs using a phase-based workflow?▼

Identify root causes of production bugs by applying a four-phase workflow: Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, and Implementation. Start with Phase 1 before proposing any fixes.

Can I apply systematic debugging to test failures and integration issues?▼

Yes, you can apply systematic debugging to test failures and integration issues. The framework enforces root cause identification across diverse issues before applying fixes, ensuring robust learning and auditability.

What is defense-in-depth in software debugging and how does it prevent regression?▼

Defense-in-depth in debugging prevents regression by tracing data flow and adding validations across multiple stack layers. This surfaces root causes and stops regressions by enforcing explicit STOP rules when shortcuts are attempted.

Why do my bug fixes keep introducing new problems, and how do I stop regressive changes?▼

Your bug fixes keep introducing new problems because of applying shortcuts without identifying the root cause. Stop regressive changes by using explicit STOP rules and stack-trace instrumentation to enforce a phase-based debugging process.

Related Skills

Explore More Software Engineering Skills→
danmestasdanmestas
4

systematic-debugging

Trace bugs to root causes via phase-based investigation and call stack analysis.

Community
Advanced
DYAI2025DYAI2025

regression-test-generator

Generate Arrange-Act-Assert regression tests for Jest, Vitest, pytest, or Playwright.

Community
Intermediate
mwaymway
4

systematic-debugging

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

Community
Advanced
jayhjenkinsjayhjenkins
1

root-cause-diagnosis

Diagnose metric anomaly root causes using 4-dimension segmentation and hypothesis testing.

Community
Basic