skills.rest
gujiachun-rainbow
gujiachun-rainbowCOMMUNITY
Explore all skills by this author →
GitHub

Systematic Debugging

Guide root-cause investigation through a four-phase debugging framework.

8|1|Updated Apr 15, 2026
Search Tags:#debugging#implementation#systematic#phases#hypothesis#root-cause
One-click install
npx skills add https://github.com/gujiachun-rainbow/RainClaw --skill systematic-debugging-gujiachun-rainbow
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Systematic Debugging
Source: https://github.com/gujiachun-rainbow/RainClaw/tree/main/.trae/skills/systematic-debugging
Command: npx skills add https://github.com/gujiachun-rainbow/RainClaw --skill systematic-debugging-gujiachun-rainbow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic Debugging provides a four-phase framework to guarantee root-cause investigation before any fixes, preventing symptom-based patches and rushed conclusions.

Core Features & Use Cases

  • Phase-driven workflow: mandatory completion of Phase 1-4 with explicit rules to avoid shortcuts.
  • Anti-patterns and guardrails: explicit warnings against time-pressure fixes and premature assumptions.
  • Cross-skill integrations: designed to work with related skills like root-cause tracing and testing to ensure robust resolution.

Quick Start

Load the Systematic Debugging skill and begin with Phase 1: Root Cause Investigation prior to proposing any fixes.

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 software bugs before applying a fix?▼

Root-cause debugging requires a systematic four-phase framework that enforces complete investigation before proposing any fixes, preventing symptom-based patches. You must finish Phase 1 hypothesis validation prior to moving to subsequent resolution phases.

What is the best way to stop applying quick patches to production issues?▼

Systematic debugging prevents quick patches by enforcing a phase-driven workflow with explicit anti-patterns and guardrails against time-pressure fixes. It mandates thorough root-cause investigation phases to ensure rushed conclusions are avoided.

How do I debug test failures systematically instead of guessing the solution?▼

Debug test failures using a four-phase workflow that mandates hypothesis-driven root-cause tracing before any implementation. The framework specifies explicit rules to avoid shortcuts and premature assumptions during the investigation process.

Can I use a systematic debugging framework for performance and integration problems?▼

Yes, the systematic debugging framework applies to software bugs, test failures, production issues, and performance or integration problems. It enforces mandatory phase completion to guarantee fixes address the actual root cause.

What are the limitations of rushing fixes without a root-cause investigation?▼

Rushing fixes without root-cause investigation leads to symptom-based patches and recurring issues due to premature assumptions. The framework defines explicit anti-patterns to prevent these time-pressure fixes and ensure robust resolution.

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
machenjiemachenjie
4

regression-testing

Create regression tests that fail on pre-fix code and pass on post-fix code.

Community
Advanced
chadanandachadananda

systematic-debugging

Guide engineers through a four-phase root-cause debugging workflow.

Community
Basic
csuzngjhcsuzngjh
1

inject-rule

Appends user-provided rule arguments to the Ad-hoc Rules section of USER_CONTEXT.md.

Community
Basic