systematic-debugging

Trace technical bugs to root causes before proposing fixes.

131|4|Updated Apr 1, 2026

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

Ready to run

npx skills add https://github.com/AlphaLab-USTC/OhMyCode --skill systematic-debugging-alphalab-ustc

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/AlphaLab-USTC/OhMyCode/tree/main/.agents/skills/superpowers/systematic-debugging
Command: npx skills add https://github.com/AlphaLab-USTC/OhMyCode --skill systematic-debugging-alphalab-ustc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This Skill helps you debug technical issues without guessing, preventing time-wasting symptom fixes that create new bugs or hide the real problem.

Core Features & Use Cases

Root Cause Investigation: Read errors carefully, reproduce reliably, check recent changes, and trace failures back to their origin.
Pattern Analysis and Hypothesis Testing: Compare against working examples, form a single testable hypothesis, and verify it with the smallest possible change.
Safe Implementation: Create a failing test first, implement one fix at a time, and re-analyze if the first attempt does not work.
Use Case: A build is failing in CI, a test is flaky, or a production bug appears under pressure and you need a disciplined process to resolve it correctly.

Quick Start

Use the systematic-debugging skill to investigate the bug from the first error message to the root cause before proposing any fix.

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 flaky test failures instead of just guessing?▼

To find the root cause of flaky test failures, you must trace symptoms back to their origin by reading errors carefully, reproducing evidence reliably, and forming a single testable hypothesis before proposing any fix.

What is the best way to debug production incidents in multi-component systems?▼

Debugging production incidents in multi-component systems requires tracing symptoms back to their root cause before any fix is proposed, applying hypothesis-driven testing to prevent time-wasting symptom fixes that create new bugs.

How do I troubleshoot performance regressions without creating new bugs?▼

Troubleshooting performance regressions without creating new bugs involves investigating technical issues by comparing against working examples, verifying a single testable hypothesis with the smallest possible change, and implementing one fix at a time.

Can I use hypothesis testing to fix CI build failures reliably?▼

Yes, you can use hypothesis testing to fix CI build failures by tracing the first error message to its origin, forming a single testable hypothesis, and creating a failing test first to verify the fix before implementation.

Why does fixing symptoms directly cause thrashing in complex technical bugs?▼

Fixing symptoms directly causes thrashing in complex technical bugs because it hides the real problem and creates new bugs, which is why a disciplined process to trace failures back to their root cause is required.