skills.rest
MomoDaviluke
MomoDavilukeCOMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

Identify root causes of bugs and failed tests through a four-phase evidence-driven process.

2|Updated Mar 3, 2026
Search Tags:#testing#defense-in-depth#phases#root-cause-analysis#systematic-debugging#debugging-process#bug-tracing
One-click install
npx skills add https://github.com/MomoDaviluke/star-citizen-promotion --skill systematic-debugging-momodaviluke
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/MomoDaviluke/star-citizen-promotion/tree/main/.trae/skills/systematic-debugging
Command: npx skills add https://github.com/MomoDaviluke/star-citizen-promotion --skill systematic-debugging-momodaviluke

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identifying root causes of bugs and failed tests by applying a four-phase, evidence-driven debugging process before proposing fixes.

Core Features & Use Cases

  • Phase-driven investigation (Phase 1: root-cause survey, Phase 2: pattern analysis, Phase 3: hypothesis testing, Phase 4: implementation with tests)
  • Anti-shortcut governance to resist time-pressure fixes
  • Documentation and defense-in-depth to prevent regressions across multiple layers

Quick Start

Follow Phase 1 through Phase 4 to systematically identify the root cause before any fix, document evidence, and add defenses to prevent future regressions.

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

To find the root cause of a bug, apply a four-phase evidence-driven debugging process: survey the root cause, analyze patterns, test hypotheses, and implement fixes with validation to resist quick shortcuts.

What is a systematic debugging process for failed tests?▼

A systematic debugging process for failed tests enforces sequential phases: root-cause survey, pattern analysis, hypothesis testing, and documented implementation with defense-in-depth to prevent future regressions.

How do I prevent regressions when fixing software bugs?▼

Prevent regressions during bug fixes by enforcing hypothesis validation, explicit documentation of evidence, and adding defense-in-depth across multiple layers before finalizing the implementation.

What's the best way to debug under time pressure without taking shortcuts?▼

The best way to debug under time pressure is using an anti-shortcut governance framework that mandates a four-phase investigation, ensuring quick fixes do not bypass root-cause analysis and validation.

Does systematic bug tracing work for incident response scenarios?▼

Yes, systematic bug tracing works for incident response scenarios by applying evidence-driven phases and defense-in-depth documentation to identify root causes and prevent recurrence during critical software engineering events.

Related Skills

Explore More Software Engineering Skills→
allexcdallexcd

autonomous-bug-fixing

Diagnose, reproduce, and fix code defects from bug reports or error logs.

Community
Advanced
CraftsMan-LabsCraftsMan-Labs
33

systematic-debugging

Trace bugs to their original trigger using defense-in-depth analysis.

Community
Advanced
lv7devlv7dev

debugging

Investigate root causes before implementing fixes through a four-phase debugging workflow.

Community
Advanced
hoanghd218hoanghd218

debug

Trace bugs to root causes using systematic debugging phases and validation.

Community
Advanced