skills.rest
herdiansah
herdiansahCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

systematic-debugging

Guide users through a four-phase process to identify root causes of technical issues.

23|2|Updated Jan 19, 2026
Search Tags:#testing#debugging#troubleshooting#error handling#root cause analysis#bug fixing
One-click install
npx skills add https://github.com/herdiansah/Antigravity-Skills-Master --skill systematic-debugging-herdiansah
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/herdiansah/Antigravity-Skills-Master/tree/main/.agent/skills/systematic-debugging
Command: npx skills add https://github.com/herdiansah/Antigravity-Skills-Master --skill systematic-debugging-herdiansah

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents wasted time and the introduction of new bugs by enforcing a rigorous, systematic approach to debugging, ensuring that the root cause of any issue is identified before any fixes are attempted.

Core Features & Use Cases

  • Root Cause Investigation: Guides users through careful error message analysis, reproduction steps, and change tracking.
  • Multi-Component Debugging: Provides a framework for gathering evidence across different system layers.
  • Hypothesis-Driven Testing: Encourages a scientific method for proposing and testing potential solutions.
  • Use Case: When a critical test fails in a CI/CD pipeline, this Skill ensures the engineer doesn't just "patch" the test but systematically investigates why it's failing, traces the data flow, and identifies the underlying code or configuration issue.

Quick Start

Use the systematic-debugging skill to investigate the root cause of the recent build failure.

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 do I need it for troubleshooting?▼

Systematic debugging is a four-phase process to identify the root cause of technical issues before implementing fixes. You need it when investigating unexpected behavior, bugs, or test failures to prevent wasted time and avoid introducing new bugs.

How do I find the root cause of a failing test or unexpected error?▼

To find the root cause of a failing test, analyze error messages, establish reproduction steps, trace data flow across system layers, and test hypotheses systematically before applying a verified fix.

What is the best way to debug multi-component systems with complex data flows?▼

Debugging multi-component systems requires gathering evidence across different system layers and tracing data flow. This approach ensures you identify the underlying code or configuration issue rather than just patching symptoms.

Can I use hypothesis-driven testing to fix bugs without introducing new issues?▼

Yes, hypothesis-driven testing applies a scientific method to propose, test, and verify potential solutions. This ensures the root cause is identified and fixes are verified before implementation, preventing new bugs.

Why does patching a failing CI/CD pipeline test often lead to recurring build failures?▼

Patching a failing test without systematic debugging often misses the underlying code or configuration issue. Tracing data flow and investigating root causes ensures the actual problem is resolved rather than just the symptom.

Related Skills

Explore More Software Engineering Skills→
sQVesQVe

debug-issue

Diagnose bugs by tracing evidence and generating a BR issue template.

Community
Advanced
MovchanetsMovchanets

debugger

Diagnose software errors by tracing stack traces to root causes.

Community
Intermediate
CodingCossackCodingCossack
19

systematic-debugging

Trace data flow to identify root causes of software bugs.

Community
Advanced
slantviewslantview
1

error-detective

Correlate error patterns and stack traces across logs and codebases.

Community
Intermediate