skills.rest
rafifos
rafifosCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

systematic-debugging

Identify root causes of bugs through a four-phase debugging process.

6|Updated Mar 24, 2019
Search Tags:#debugging#defense-in-depth#phases#root-cause#systematic-debugging#root-cause-tracing
One-click install
npx skills add https://github.com/rafifos/dotfiles --skill systematic-debugging-rafifos
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/rafifos/dotfiles/tree/main/dot_agents/skills/systematic-debugging
Command: npx skills add https://github.com/rafifos/dotfiles --skill systematic-debugging-rafifos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic Debugging helps engineers reliably identify root causes behind bugs and failures before applying fixes. It eliminates guesswork under pressure by enforcing a structured process that prioritizes durable fixes over quick patches.

Core Features & Use Cases

  • Phase 1 Root Cause Investigation: Read errors, reproduce, gather evidence.
  • Phase 2 Pattern Analysis: Find working examples and compare patterns.
  • Phase 3 Hypothesis and Testing: Form a single hypothesis and test minimally.
  • Phase 4 Implementation: Create tests, implement the root cause fix, verify.
  • Anti-patterns and defense-in-depth: Avoid shortcuts and add multi-layer safeguards.
  • Testing approach: Narrative-driven validation across scenarios to ensure reliability.

Quick Start

Load the skill and follow the four phases in order to identify root causes before proposing fixes.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema
What is systematic debugging and when should I use it?▼

Systematic debugging is a structured process to identify root causes behind bugs before applying fixes. Use it during software development, CI failures, production incidents, and flaky tests, especially under time pressure.

How do I find the root cause of a bug instead of just patching symptoms?▼

To find the root cause, follow a four-phase process: investigate errors and gather evidence, analyze patterns by comparing working examples, form and test a single hypothesis, then implement the fix with validation.

What are the steps to reproduce and fix flaky tests or CI failures?▼

Fix flaky tests or CI failures by gathering evidence and reproducing the error first, then comparing against passing patterns, testing a single minimal hypothesis, and finally implementing the root cause fix with regression tests.

Why do my bug fixes keep causing regressions in production incidents?▼

Bug fixes cause regressions when engineers chase symptoms instead of root causes. Applying a structured, four-phase debugging process with defense-in-depth safeguards ensures traceable, lasting resolutions rather than quick patches.

What are common anti-patterns when debugging production incidents under time pressure?▼

Common anti-patterns include skipping evidence gathering, chasing symptoms, and applying quick patches without testing. Systematic debugging enforces explicit validation and a defense-in-depth mindset to avoid these shortcuts.

Does systematic debugging work for all types of software failures?▼

Yes, systematic debugging works across software development, CI failures, production incidents, and flaky tests. It enforces a structured process of root cause investigation, pattern analysis, hypothesis testing, and validated implementation.

Related Skills

Explore More Software Engineering Skills→
shimaMatzshimaMatz

kiro-debug

Identify failure root causes from logs and runtime evidence.

Community
Advanced
handsomelong922handsomelong922

systematic-debugging

Enforce a four-phase root-cause debugging process before applying fixes.

Community
Advanced
felix-howardfelix-howard

ck:debug

Guide systematic debugging through investigation, analysis, testing, and implementation.

Community
Advanced
benthamitebenthamite
9

systematic-debugging

Guide a four-phase debugging process to identify and resolve root causes.

Community
Advanced