skills.rest
Marshall-Hallenbeck
Marshall-HallenbeckCOMMUNITY
Explore all skills by this author →
𝕏@mjhallenbeckGitHub

systematic-debugging

Enforce a four-phase scientific debugging methodology for root cause resolution.

5|1|Updated Oct 18, 2019
Search Tags:#testing#software engineering#debugging#root cause#troubleshooting#data flow
One-click install
npx skills add https://github.com/Marshall-Hallenbeck/dot_files --skill systematic-debugging-marshall-hallenbeck
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/Marshall-Hallenbeck/dot_files/tree/main/.claude/skills/systematic-debugging
Command: npx skills add https://github.com/Marshall-Hallenbeck/dot_files --skill systematic-debugging-marshall-hallenbeck

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill prevents the common pitfall of applying superficial patches to symptoms, which often leads to recurring issues and technical debt. It enforces a disciplined, scientific approach to identifying and resolving the actual root cause of technical failures.

Core Features & Use Cases

  • Root Cause Investigation: Provides a structured framework to trace data flow and identify the origin of errors before attempting any fixes.
  • Hypothesis-Driven Testing: Guides the user through the scientific method to ensure changes are minimal, verifiable, and targeted.
  • Architectural Review: Triggers a mandatory pause and evaluation when multiple fix attempts fail, preventing "thrashing" in complex systems.

Quick Start

Apply the systematic debugging process to investigate the current test failure by tracing the data flow from the error back to the source.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema
What is root cause analysis in software debugging?▼

Root cause analysis in software debugging is a scientific methodology that traces data flow back to the origin of errors before attempting fixes, preventing superficial patches that cause recurring technical debt.

How do I debug recurring test failures systematically?▼

Debug recurring test failures systematically by applying a structured four-phase methodology that traces data flow from the error back to the source, ensuring changes are minimal, verifiable, and targeted.

When should I use hypothesis-driven testing for troubleshooting?▼

Use hypothesis-driven testing for troubleshooting when quick-fix attempts have proven ineffective, requiring adherence to structured investigation, hypothesis testing, and architectural validation protocols.

What is the best way to stop thrashing when fixing complex software bugs?▼

The best way to stop thrashing when fixing complex software bugs is to trigger a mandatory architectural review and evaluation pause after multiple fix attempts fail, preventing further unstructured changes.

Does scientific debugging work for production incidents?▼

Scientific debugging works for production incidents by enforcing a disciplined investigation process that identifies and resolves the actual root cause instead of applying superficial patches to symptoms.

Related Skills

Explore More Software Engineering Skills→
nzkbuildnzkbuild
3

steroid-diagnose

Guide root cause investigation through error analysis, reproduction, and data flow tracing.

Community
Advanced
dmae97dmae97
130

omk-flow-bugfix

Guide bug resolution from reproduction evidence to root-cause analysis and minimal code changes.

Community
Intermediate
WladimirfnWladimirfn

bug-hunter

Reproduce software bugs, trace execution flow, identify root cause, and fix with regression tests.

Community
Advanced
thavirak-svaythavirak-svay
1

systematic-debugging

Debug software issues through four phases of root cause investigation and testing.

Community
Advanced