skills.rest
anortham
anorthamCOMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

Identify root causes through evidence gathering, pattern analysis, and hypothesis testing.

2|Updated Mar 3, 2026
Search Tags:#debugging#defense-in-depth#quality#tracing#risk-management#root-cause#phase-based
One-click install
npx skills add https://github.com/anortham/razorback --skill systematic-debugging-anortham
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/anortham/razorback/tree/main/skills/systematic-debugging
Command: npx skills add https://github.com/anortham/razorback --skill systematic-debugging-anortham

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging helps teams stop guessing and ensures root causes are found before proposing fixes, reducing waste and rework.

Core Features & Use Cases

  • Phase-based workflow (Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, Implementation) to ensure disciplined, repeatable debugging.
  • Defense-in-depth mindset with multiple validation layers and instrumentation to prevent regression and data issues.
  • Real-world applicability across production incidents, test failures, performance problems, and integration challenges.

Quick Start

Load the skill and begin Phase 1: Root Cause Investigation to gather evidence 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 before attempting a fix?▼

To find a root cause before fixing, gather evidence, analyze patterns, and test hypotheses systematically. This phase-driven debugging approach eliminates guesswork and reduces wasted effort on ineffective patches.

What is the best way to debug production incidents and test failures systematically?▼

The best way to debug production incidents and test failures is applying a four-phase workflow: root cause investigation, pattern analysis, hypothesis testing, and validated implementation with guardrails to prevent regression.

Does systematic debugging work for performance problems and integration issues?▼

Yes, systematic debugging works for performance problems and integration issues across codebases by enforcing evidence gathering and hypothesis testing before applying fixes, ensuring repeatable and disciplined problem resolution.

How do I prevent regression when implementing a bug fix?▼

To prevent regression during a bug fix, apply a defense-in-depth mindset with multiple validation layers and instrumentation. This ensures the validated implementation catches data issues and prevents future failures.

Why does my debugging process result in constant rework and wasted effort?▼

Debugging results in rework and wasted effort when root causes are not identified before proposing fixes. Enforcing evidence gathering and pattern analysis before implementation stops the cycle of guessing and ineffective patching.

Related Skills

Explore More Software Engineering Skills→
jk278jk278

debugging-assistant

Diagnose software bugs from stack traces and 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

debugging

Investigate root causes before implementing fixes through a four-phase debugging workflow.

Community
Advanced
assofohdzassofohdz
25

diagnose

Diagnose intermittent software bugs and performance regressions through a disciplined debugging workflow.

Community
Advanced