systematic-debugging

Trace errors, reproduce bugs, and identify root causes before proposing fixes.

Updated May 24, 2026

Search Tags:#debugging #root cause #troubleshooting #test failures #hypothesis testing #bug investigation

Ready to run

npx skills add https://github.com/anxiety135790/hermes-skills --skill systematic-debugging-anxiety135790

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/anxiety135790/hermes-skills/tree/main/software-development/systematic-debugging
Command: npx skills add https://github.com/anxiety135790/hermes-skills --skill systematic-debugging-anxiety135790

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you debug technical issues by forcing a disciplined root-cause-first process instead of guessing, patching symptoms, or making risky changes under pressure.

Core Features & Use Cases

Root Cause Investigation: Read error messages, reproduce failures, inspect recent changes, and trace data flow to understand why an issue is happening.
Pattern Analysis: Compare broken behavior against working examples to identify meaningful differences and dependencies.
Hypothesis Testing: Form a single testable theory, make the smallest possible change, and verify results before moving forward.
Safe Implementation: Create a regression test, apply one fix at a time, and stop to reassess if repeated attempts fail.
Use Case: A build is failing in CI and the obvious workaround is tempting; this Skill guides the investigation so the real defect is found and fixed cleanly.

Quick Start

Use the systematic-debugging skill to investigate this failure step by step, identify the root cause, and recommend the smallest safe fix.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema

What is the best way to find the root cause of test failures and production bugs?▼

Systematic debugging identifies root causes by tracing errors, reproducing failures, and testing a single hypothesis at a time to prevent symptom-only patches.

How do I investigate a failing CI build without guessing the fix?▼

Investigate a failing CI build by reading error messages, inspecting recent changes, and tracing data flow to understand the failure before making any changes.

How do I troubleshoot performance regressions in a multi-component system?▼

Troubleshoot performance regressions by comparing broken behavior against working examples to identify dependencies, then form a single testable theory to verify results.

Why should I create a regression test before fixing a bug?▼

Create a regression test before fixing a bug to ensure safe implementation, applying one fix at a time and verifying results to prevent symptom-only patches.

What should I do when repeated bug fixes fail to resolve the issue?▼

When repeated bug fixes fail, stop to reassess your hypothesis, gather more evidence, and verify a single change instead of making risky changes under pressure.

Can I use hypothesis testing to diagnose build issues and complex system problems?▼

Yes, use hypothesis testing to diagnose build issues by forming a single testable theory, making the smallest possible change, and verifying results before moving forward.