skills.rest
mattniedelman
mattniedelmanCOMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

Guide engineers through a four-phase root-cause debugging process.

1|Updated Dec 25, 2017
Search Tags:#debugging#codebase#systematic#tracing#reproduce#root-cause
One-click install
npx skills add https://github.com/mattniedelman/dotfiles --skill systematic-debugging-mattniedelman
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/mattniedelman/dotfiles/tree/main/dot_augment/skills/systematic-debugging
Command: npx skills add https://github.com/mattniedelman/dotfiles --skill systematic-debugging-mattniedelman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging guides engineers to identify root causes before applying fixes, reducing wasted time and rework.

Core Features & Use Cases

  • Provides a structured, four-phase approach (Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, Implementation) to debugging.
  • Helps teams reproduce issues consistently, gather evidence, and trace data flow to the source of a bug.
  • Improves confidence in fixes by enforcing verification before closure and preventing symptom-only patches.

Quick Start

Outline a four-phase root-cause investigation plan for a failing feature, including steps to reproduce, evidence collection, and data-flow tracing.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema
How do I identify the root cause of a bug before applying a fix?▼

To identify a root cause before fixing a bug, follow a systematic debugging process that reproduces issues consistently, gathers evidence, and traces data flow to the source, preventing wasted time on symptom-only patches.

What is the best way to systematically debug production issues?▼

Systematic debugging resolves production issues using a four-phase process: Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, and Implementation, ensuring reliable fixes through evidence collection and verification before closure.

How do I reproduce software bugs consistently during root cause investigation?▼

Reproduce software bugs consistently by outlining a root-cause investigation plan that includes specific steps to reproduce the failure, collect evidence, and trace data flow patterns to pinpoint the origin.

Why does applying quick fixes lead to recurring codebase bugs?▼

Applying quick fixes leads to recurring codebase bugs because symptom-only patches bypass root cause identification, whereas systematic debugging enforces hypothesis testing and verification to prevent rework.

Can I use systematic debugging for any software project or just production issues?▼

You can use systematic debugging across any software project and production issues, as its four-phase approach to tracing root causes and verifying fixes applies universally to resolving codebase failures reliably.

Related Skills

Explore More Software Engineering Skills→
sQVesQVe

debug-issue

Diagnose bugs by tracing evidence and generating a BR issue template.

Community
Advanced
rakhnianskii9rakhnianskii9

regression-suite

Generate a regression test manifest and status reports from sprint plans and test inventories.

Community
Advanced
fratilanicofratilanico
7

systematic-debugging

Trace bugs to root causes through call chains and data flow.

Community
Advanced
chicanoandres702chicanoandres702

error-detective

Correlate logs, stack traces, and anomalies to diagnose distributed system errors.

Community
Advanced