skills.rest
cill-i-am
cill-i-amCOMMUNITY
Explore all skills by this author →
𝕏@cillo_bGitHub

systematic_debugging

Diagnose software bugs through root-cause investigation before implementing fixes.

Updated Apr 1, 2026
Search Tags:#debugging#defense-in-depth#systematic#traceability#phases#root-cause
One-click install
npx skills add https://github.com/cill-i-am/task-tracker --skill systematic-debugging-cill-i-am
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic_debugging
Source: https://github.com/cill-i-am/task-tracker/tree/main/.agents/skills/systematic-debugging
Command: npx skills add https://github.com/cill-i-am/task-tracker --skill systematic-debugging-cill-i-am

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Random fixes waste time and create new bugs. Always find root cause before attempting fixes. Symptom fixes are failure.

Core Features & Use Cases

  • Four-phase debugging framework (Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, Implementation) to ensure disciplined problem-solving.
  • Anti-patterns and defense-in-depth guidance that resist time-pressure rationalization.
  • Structured data-flow tracing, evidence gathering, and validated completion criteria to prevent regression.

Quick Start

Load the skill and follow the four phases to diagnose and fix issues systematically.

Frequently Asked Questions about systematic_debugging

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why should I systematically find a root cause before fixing a software bug?▼

Systematic debugging enforces root-cause investigation before fixes, preventing symptom patches that waste time and introduce regressions. It uses evidence gathering and pattern analysis to target the actual underlying issue.

How do I debug production outages and test failures systematically?▼

Debug production outages and test failures by following four phases: root cause investigation, pattern analysis, hypothesis and testing, then implementation, incorporating evidence gathering and defense-in-depth guidance to prevent regressions.

What is the best way to trace data flow and gather evidence during debugging?▼

The best way to trace data flow and gather evidence is applying a structured debugging framework requiring completion of root cause investigation and pattern analysis phases before fixes, ensuring validated completion criteria are met.

Can I use this systematic debugging approach for performance issues across any codebase?▼

Yes, this systematic debugging approach applies to performance issues across any codebase. It diagnoses unexpected behavior by enforcing structured data-flow tracing and hypothesis testing regardless of the software environment.

Does systematic debugging help avoid anti-patterns when fixing bugs under time pressure?▼

Systematic debugging helps avoid anti-patterns under time pressure by incorporating defense-in-depth guidance. This framework resists rationalization and enforces validated completion criteria to prevent regression during fixes.

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
lagz0nelagz0ne
2

systematic-debugging

Guide engineers through a four-phase debugging process to uncover root causes.

Community
Advanced
mwaymway
4

systematic-debugging

Identify root causes of bugs and test failures through a four-phase debugging workflow.

Community
Advanced
openaeonopenaeon
87

systematic-debugging

Investigate software bugs through a four-phase root-cause workflow with evidence gathering.

Community
Intermediate