skills.rest
79yuuki
79yuukiCOMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

Investigate software bugs to identify root causes before implementing fixes.

1|Updated Mar 6, 2014
Search Tags:#software engineering#debugging#root cause#verification#test failures#hypothesis testing#bug investigation
One-click install
npx skills add https://github.com/79yuuki/dotfiles --skill systematic-debugging-79yuuki
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/79yuuki/dotfiles/tree/main/claude/skills/systematic-debugging
Command: npx skills add https://github.com/79yuuki/dotfiles --skill systematic-debugging-79yuuki

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents wasted debugging cycles caused by random patches, symptom fixes, and guesswork by enforcing a structured root cause investigation process before changes are made.

Core Features & Use Cases

  • Root Cause Investigation: Guides engineers through evidence gathering, reproduction, change analysis, and data flow tracing before proposing solutions.
  • Hypothesis-Driven Debugging: Provides a disciplined process for forming single hypotheses, testing minimally, and avoiding multiple simultaneous fixes.
  • Failure Prevention Practices: Helps resolve bugs, test failures, build issues, performance problems, and integration problems with validation and verification steps.

Quick Start

Use the systematic-debugging skill to investigate this bug and find the root cause before suggesting any fixes.

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 software bugs before applying fixes?▼

To find the root cause of software bugs, you must enforce a structured investigation process that includes evidence gathering, reproduction, change analysis, and data flow tracing before proposing any solutions.

What is hypothesis-driven debugging and how does it prevent symptom-based fixes?▼

Hypothesis-driven debugging is a disciplined process of forming a single hypothesis, testing it minimally, and avoiding multiple simultaneous fixes to prevent random patches and symptom-based guesswork.

How do I investigate test failures and production incidents systematically?▼

You investigate test failures and production incidents systematically by applying structured evidence gathering, change analysis, and verification practices to trace data flow and identify the underlying issue.

What is the best way to debug build failures and performance problems without guessing?▼

The best way to debug build failures and performance problems without guessing is to follow a structured root cause investigation workflow that requires evidence gathering and hypothesis testing before changes are made.

Why do my bug fixes keep causing new issues in integration and performance workflows?▼

Bug fixes cause new issues when they address symptoms rather than root causes; a disciplined investigation process with validation and verification steps prevents this by testing single hypotheses minimally.

Related Skills

Explore More Software Engineering Skills→
mkalkeremkalkere
4

debugging

Reproduce, isolate, and diagnose code failures with evidence-based techniques.

Community
Advanced
a-ariffa-ariff
14

root-cause-tracing

Trace bugs backward from symptoms to identify root causes.

Community
Intermediate
zinohomezinohome
1

flaky-test-detective

Diagnose flaky test patterns and run detection scripts for intermittent failures.

Community
Advanced
act70255act70255

code-reviewer

Automate code reviews with static analysis and AI vulnerability detection.

Community
Advanced