skills.rest
Hohlas
HohlasCOMMUNITY
Explore all skills by this author →
Website𝕏@Hohla2010GitHub

systematic-debugging

Guide structured debugging through four phases before applying fixes.

3|Updated Jun 3, 2022
Search Tags:#debugging#defense-in-depth#reliability#tracing#root-cause#phase-based
One-click install
npx skills add https://github.com/Hohlas/SoSimple --skill systematic-debugging-hohlas
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/Hohlas/SoSimple/tree/main/.kilocode/skills/systematic-debugging
Command: npx skills add https://github.com/Hohlas/SoSimple --skill systematic-debugging-hohlas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guiding teams to avoid guesswork by enforcing root-cause investigation before fixes, reducing firefighting and regression risk.

Core Features & Use Cases

  • Phase-driven framework with four mandatory phases (Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, Implementation) to prevent shortcut fixes.
  • Anti-patterns and guardrails that resist time-pressure rationalization and encourage thorough analysis.
  • Techniques for root-cause tracing, defense-in-depth validation, and structured debugging across complex systems.
  • Practical scenarios and reference materials that improve reliability in production environments.

Quick Start

Load the systematic-debugging skill and begin with Phase 1 root-cause investigation 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 root-cause debugging and how does it differ from symptom fixing?▼

Root-cause debugging locates the underlying cause behind bugs before applying fixes, preventing symptom fixes that cause regressions. It enforces a structured 4-phase workflow to guide teams away from guesswork and firefighting.

How do I structure a debugging session to avoid applying shortcut fixes?▼

Structure a debugging session using a 4-phase workflow: Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, and Implementation. This enforces thorough analysis and prevents shortcut fixes driven by time pressure.

Can I use systematic debugging for incident response in production environments?▼

Yes, systematic debugging applies to incident response in production environments. It provides practical scenarios and defense-in-depth validation across multiple layers to improve reliability during complex incidents.

What's the best way to trace bugs when symptoms mislead the team?▼

The best way to trace misleading bugs is root-cause tracing combined with pattern analysis. By investigating hypotheses before implementing fixes, teams resist time-pressure rationalization and avoid being misled by symptoms.

Why does my team keep fixing symptoms instead of finding the actual bug?▼

Teams fix symptoms instead of root causes due to time-pressure rationalization and lack of guardrails. Anti-patterns and a mandatory phase-based debugging workflow resist guesswork, ensuring thorough root-cause investigation before fixes.

Does defense-in-depth validation work across multiple layers of a complex system?▼

Yes, defense-in-depth validation works across multiple layers of complex systems. It provides structured debugging techniques that validate fixes thoroughly, reducing regression risk and improving overall system reliability.

Related Skills

Explore More Software Engineering Skills→
rbah31rbah31
5

runbook

Investigate production symptoms and generate structured incident reports from logs, metrics, and traces.

Community
Intermediate
romiluz13romiluz13
161

debugging-patterns

Enforce root-cause investigation before applying fixes in debugging workflows.

Community
Advanced
jonkikyjonkiky

investigate

Trace reported issue symptoms to code paths and verify root cause hypotheses.

Community
Advanced
LuizfbmLuizfbm
1

systematic-debugging

Investigate software defects by mandating root cause analysis before implementing fixes.

Community
Advanced