skills.rest
GuicedEE
GuicedEEOFFICIAL
Explore all skills by this author →
WebsiteGitHub

systematic-debugging

Identify root causes of bugs using a five-step debugging workflow.

5|Updated Jul 6, 2025
Search Tags:#workflow#debugging#investigation#diagnostics#traceability#root-cause
One-click install
npx skills add https://github.com/GuicedEE/ai-rules --skill systematic-debugging-guicedee
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/GuicedEE/ai-rules/tree/main/skills/.curated/systematic-debugging
Command: npx skills add https://github.com/GuicedEE/ai-rules --skill systematic-debugging-guicedee

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The skill helps engineers systematically identify the root cause of bugs and failures before proposing fixes, reducing guesswork and rework.

Core Features & Use Cases

  • Reproduce and capture exact steps and error output.
  • Localize the smallest failing scope and trace data/control flow to the first wrong state.
  • Apply the five-step workflow (Reproduce, Localize, Trace, Fix, Verify) with diagnostic instrumentation and cross-checks like root-cause tracing and defense-in-depth.

Quick Start

Start by collecting error messages and steps to reproduce, then follow the five-step workflow to pinpoint the original trigger before proposing any fixes.

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 how does it help find a root cause?▼

Systematic debugging is a structured workflow to identify the root cause behind bugs before proposing fixes. It reduces guesswork by guiding you through reproducibility, localization, tracing, fixes, and verification.

How do I debug flaky test failures when the error is inconsistent?▼

Debug flaky test failures by first capturing exact steps to reproduce the error output. Then localize the smallest failing scope, trace data flow to the first wrong state, and apply diagnostic instrumentation to verify the fix.

What is the best way to investigate unexpected application behavior before changing code?▼

The best way to investigate unexpected behavior is to follow a five-step workflow: Reproduce, Localize, Trace, Fix, and Verify. This ensures you pinpoint the original trigger through root-cause tracing before proposing any fixes.

Does root-cause tracing work for any debugging scenario or only specific test failures?▼

Root-cause tracing applies across any debugging scenario where tests fail, errors are flaky, or unexpected behavior occurs. It enforces diagnostic instrumentation and cross-checks to localize the first wrong state.

How do I localize a bug to the smallest failing scope during investigation?▼

To localize a bug, trace data and control flow backwards from the observed error to the first wrong state. This investigation step narrows the failing scope before you apply fixes and run verification cross-checks.

Why should I add defense-in-depth after fixing a bug?▼

Defense-in-depth is integrated after verification to prevent regressions. Following the five-step debugging workflow, it provides forward-looking guidance alongside root-cause tracing to ensure the original trigger is permanently resolved.

Related Skills

Explore More Software Engineering Skills→
sQVesQVe

debug-issue

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

Community
Advanced
dmulcaheydmulcahey

systematic-debugging

Trace software bugs to root causes using a four-phase investigation methodology.

Community
Advanced
openJiuwen-aiopenJiuwen-ai
2.5k

ascend-moe-optimizer-auto-trace

Generate and validate TRACE_POINT instrumentation and Chrome trace workflows for Ascend MoE operators.

Official
Advanced
ayourtchayourtch

root-cause-tracing

Trace call stacks backward to identify the original bug trigger.

Community
Intermediate