skills.rest
tiancaiamao
tiancaiamaoCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

systematic-debugging

Diagnose software bugs by enforcing root-cause investigation before proposing fixes.

5|Updated Feb 8, 2026
Search Tags:#software engineering#debugging#investigation#root cause#troubleshooting#test failures#flaky tests
One-click install
npx skills add https://github.com/tiancaiamao/ai --skill systematic-debugging-tiancaiamao
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/tiancaiamao/ai/tree/main/skills/systematic-debugging
Command: npx skills add https://github.com/tiancaiamao/ai --skill systematic-debugging-tiancaiamao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents wasted effort on quick fixes by forcing a disciplined root-cause investigation before any remediation is proposed.

Core Features & Use Cases

  • Root-cause first workflow: Read errors carefully, reproduce the issue, check recent changes, and trace the data flow before fixing.
  • Pattern and hypothesis analysis: Compare against working examples, identify differences, form one clear hypothesis, and test it minimally.
  • Safety against thrashing: Handles failed fixes, time pressure, flaky behavior, and multi-component failures without resorting to guesswork.
  • Use case: A production incident or failing test is diagnosed systematically so the actual source is fixed instead of masking symptoms.

Quick Start

Use the systematic-debugging skill to investigate this bug from root cause to verified 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 patching symptoms?▼

Systematic debugging prevents wasted effort on quick fixes by enforcing a disciplined root-cause investigation workflow. It requires reading errors, reproducing the issue, and tracing data flow before any remediation is proposed.

What is the best way to debug a production incident under time pressure without guessing?▼

The best way to debug a production incident under time pressure is to compare against working examples, identify differences, and form one clear hypothesis. This prevents thrashing and ensures the actual source is fixed rather than masking symptoms.

How do I troubleshoot performance regressions and multi-component integration issues systematically?▼

Troubleshoot performance regressions and multi-component integration issues by tracing data flow and comparing against working examples. Form a single hypothesis, test it minimally, and verify the smallest effective fix with tests to avoid masking symptoms.

Why do my software fixes keep failing when I try to patch bugs quickly?▼

Software fixes keep failing when quick patches mask symptoms instead of addressing the root cause. Systematic debugging handles failed fixes by requiring careful error reading, issue reproduction, and hypothesis verification before proposing a remediation.

Does root-cause debugging work for diagnosing complex software bugs with multiple failing components?▼

Root-cause debugging works for complex multi-component failures by tracing data flow and comparing against working examples. It safely handles failed fixes and time pressure without resorting to guesswork, ensuring the actual source is fixed.

Related Skills

Explore More Software Engineering Skills→
derHakenderHaken
437

systematic-debugging

Trace data flow and apply a four-phase process to fix root causes.

Community
Advanced
MissTullyMissTully

gstack-openclaw-investigate

Diagnose software issues through a phase-driven root-cause analysis workflow.

Community
Advanced
khapn-2933khapn-2933

tkm:debug-code

Guide users through a four-phase debugging framework for software issues.

Community
Advanced
DoraemonHugUDoraemonHugU
14

systematic-debugging

Systematically debugs issues from root cause investigation to implementation.

Community
Advanced