skills.rest
hochoa13
hochoa13COMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

Guide root cause analysis of software bugs through a four-phase process.

Updated Mar 13, 2026
Search Tags:#debugging#investigation#troubleshooting#software development#root cause analysis#bug fixing
One-click install
npx skills add https://github.com/hochoa13/Asistente-Harlest --skill systematic-debugging-hochoa13
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/hochoa13/Asistente-Harlest/tree/main/skills/software-development/systematic-debugging
Command: npx skills add https://github.com/hochoa13/Asistente-Harlest --skill systematic-debugging-hochoa13

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured, four-phase process to systematically investigate and resolve bugs, test failures, and unexpected behavior, ensuring root causes are identified before any fixes are attempted.

Core Features & Use Cases

  • Root Cause Investigation: Guides through careful error message analysis, reproduction steps, change tracking, and data flow tracing.
  • Pattern Analysis: Helps compare broken code against working examples and understand dependencies.
  • Hypothesis Testing: Encourages a scientific approach with single hypotheses and minimal, verifiable tests.
  • Implementation: Ensures fixes target the root cause with regression tests and defines a "Rule of Three" to question architecture if multiple fixes fail.
  • Use Case: When a critical test fails in production, this Skill ensures the team doesn't just patch the symptom but rigorously finds and fixes the underlying issue, preventing recurrence.

Quick Start

Use the systematic-debugging skill to investigate a test failure in the file 'src/user_auth.py'.

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 software bug instead of just patching the symptom?▼

To find the root cause of a software bug, follow a systematic four-phase process for investigation, ensuring you analyze error messages, reproduce the issue, and test hypotheses before implementing fixes.

What is the best way to investigate a test failure in production?▼

The best way to investigate a test failure in production is to use a structured debugging process that traces data flow, tracks recent changes, and verifies single hypotheses to resolve the underlying issue.

How do I systematically debug unexpected software behavior?▼

Systematically debug unexpected software behavior by comparing broken code against working examples, understanding dependencies, and applying minimal, verifiable tests to confirm the root cause.

When should I question my architecture during bug fixing?▼

You should question your architecture during bug fixing if multiple fixes fail, applying the "Rule of Three" to evaluate whether the current design is causing recurring unexpected behavior.

Does systematic debugging require specific tools or dependencies?▼

Systematic debugging does not require specific external dependencies; it provides a structured methodology utilizing standard tools for error analysis, reproduction, change tracking, and hypothesis testing.

How do I ensure my bug fix prevents future recurrence?▼

Ensure your bug fix prevents future recurrence by targeting the verified root cause with regression tests, confirming the fix through minimal verifiable tests before finalizing the implementation.

Related Skills

Explore More Software Engineering Skills→
michaelsvanbeekmichaelsvanbeek
1

anomaly-detection

Detect unusual patterns in time-series, logs, and metric data.

Community
Advanced
rakhnianskii9rakhnianskii9

regression-suite

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

Community
Advanced
AbdullahMalik17AbdullahMalik17
9

systematic-debugging

Identify root causes of bugs using a structured four-phase process.

Community
Advanced
UlanxxUlanxx

canary

Monitor live URLs for console errors, performance regressions, and page failures.

Community
Advanced