skills.rest
tctinh
tctinhCOMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

Guide structured four-phase debugging to identify root causes before code changes.

160|20|Updated Jan 4, 2026
Search Tags:#debugging#troubleshooting#root cause analysis#bug fixing#systematic process#error investigation
One-click install
npx skills add https://github.com/tctinh/agent-hive --skill systematic-debugging-tctinh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/tctinh/agent-hive/tree/main/packages/opencode-hive/skills/systematic-debugging
Command: npx skills add https://github.com/tctinh/agent-hive --skill systematic-debugging-tctinh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents wasted time and new bugs caused by random fixes or symptom-based patching, ensuring that the true root cause of any technical issue is identified and addressed systematically.

Core Features & Use Cases

  • Root Cause Investigation: Guides users through careful error analysis, reproduction steps, and evidence gathering in multi-component systems.
  • Pattern Analysis: Helps identify similarities between working and broken code, and understand dependencies.
  • Hypothesis Testing: Promotes a scientific approach with single hypotheses and minimal, verifiable tests.
  • Use Case: When a critical test fails in a CI pipeline, this Skill ensures the engineer doesn't just "try a quick fix" but meticulously traces the data flow and component interactions to pinpoint the exact source of the failure before proposing a solution.

Quick Start

Use the systematic-debugging skill to investigate the root cause of the recent test failures.

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

To find the root cause, follow a structured four-phase debugging process: reproduce the error consistently, examine recent changes, trace data flow across components, and formulate a single hypothesis before modifying any code.

What is the best way to systematically debug complex multi-component systems?▼

Systematic debugging of complex systems requires careful error analysis, consistent reproduction, and gathering evidence by tracing data flow through component interactions to pinpoint the exact failure source before proposing a fix.

How do I investigate CI pipeline failures without introducing new bugs?▼

Investigate CI pipeline failures by meticulously tracing the data flow and examining component interactions rather than trying a quick fix, ensuring the true root cause is addressed to prevent new bugs.

What should I do when multiple bug fixes fail to resolve an issue?▼

When multiple fixes fail, the debugging process mandates a critical step to question the underlying architecture, analyzing patterns between working and broken code to identify deeper systemic flaws.

How do I use hypothesis testing to troubleshoot errors effectively?▼

Troubleshoot errors using hypothesis testing by formulating a single hypothesis, conducting minimal verifiable tests, comparing working versus broken code patterns, and understanding dependencies before applying a fix.

Related Skills

Explore More Software Engineering Skills→
FoundationForgeFoundationForge

debug

Run structured debugging sessions to reproduce, isolate, and diagnose software errors.

Official
Intermediate
viraatdasviraatdas

investigate

Identify bug root causes by collecting symptoms, reading code, and testing hypotheses.

Community
Advanced
manuelbrandner85manuelbrandner85

diagramming-code

Generate Mermaid diagrams from Trailmark code graphs.

Community
Intermediate
UlanxxUlanxx

canary

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

Community
Advanced