skills.rest
tutur3u
tutur3uOFFICIAL
Explore all skills by this author →
Website𝕏@tutur3uGitHub

systematic-debugging

Enforce root-cause investigation before fixing software bugs.

53|33|Updated Sep 15, 2022
Search Tags:#debugging#anti-patterns#defense-in-depth#phases#root-cause#systems
One-click install
npx skills add https://github.com/tutur3u/platform --skill systematic-debugging-tutur3u
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/tutur3u/platform/tree/main/.agents/skills/systematic-debugging
Command: npx skills add https://github.com/tutur3u/platform --skill systematic-debugging-tutur3u

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a disciplined, repeatable approach to debugging, ensuring you always identify the root cause before proposing fixes.

Core Features & Use Cases

  • Phase-driven workflow: Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, and Implementation.
  • Anti-patterns and safeguards to resist time-pressure shortcuts.
  • Guidance for tracing data flow, validating across multiple layers, and defending against regressions.

Quick Start

  1. Read the overview and commit to Phase 1: Root Cause Investigation before attempting any fixes.
  2. When in doubt, consult the reference materials (root-cause-tracing.md, defense-in-depth.md, condition-based-waiting.md) for established patterns.
  3. Complete Phase 4 Implementation with a validated fix and tests.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema
How do I systematically debug software to find the root cause of a bug?▼

Systematic debugging enforces root-cause investigation before any fix by following a four-phase workflow: Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, and Implementation.

What is the best way to prevent debugging shortcuts when under time pressure?▼

To prevent debugging shortcuts under time pressure, apply built-in anti-patterns and safeguards that enforce tracing data flow and validating across multiple layers before proposing a fix.

How do I trace data flow and validate multiple layers during production debugging?▼

Production debugging requires tracing data flow and validating behavior across multiple system layers, guided by reference materials like root-cause-tracing and defense-in-depth patterns.

Does this systematic debugging approach work for test failures and unexpected system behavior?▼

Yes, this systematic debugging approach applies to test failures, production bugs, and unexpected behavior across software systems by enforcing root-cause investigation before any implementation.

What are the limitations of fixing bugs without a root cause investigation phase?▼

Fixing bugs without root cause investigation risks introducing regressions, as the four-phase workflow ensures a validated fix and tests are completed only after hypothesis testing confirms the underlying issue.

Related Skills

Explore More Software Engineering Skills→
23000311472300031147

investigate

Guide systematic debugging from symptom to root cause with four phases.

Community
Advanced
tutur3ututur3u
53

systematic-debugging

Enforce root-cause investigation before fixing software bugs.

Official
Advanced
gqf2008gqf2008

systematic-debugging

Identify software bug root causes through a four-phase debugging process.

Community
Advanced
stayconnectquickstayconnectquick

gstack-openclaw-investigate

Diagnose software issues through a phase-based debugging workflow and output a structured report.

Community
Advanced