skills.rest
limaon
limaonCOMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

Guide software engineers through a four-phase root-cause debugging workflow.

Updated Jul 8, 2022
Search Tags:#debugging#root cause#defense-in-depth#pattern-analysis#four-phase#hypothesis-testing
One-click install
npx skills add https://github.com/limaon/dotfiles --skill systematic-debugging-limaon
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/limaon/dotfiles/tree/main/.config/opencode/skills/systematic-debugging
Command: npx skills add https://github.com/limaon/dotfiles --skill systematic-debugging-limaon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams systematically identify root causes before applying fixes, preventing symptom-based work.

Core Features & Use Cases

  • Four-Phase Process: Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, Implementation.
  • Defensive Practices: Root-cause tracing and defense-in-depth to reduce recurrence.
  • Use Case: When diagnosing flaky tests, production outages, or complex bug cascades, follow the skill to locate the true trigger.

Quick Start

Read the 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 a systematic debugging workflow for finding root causes?▼

A systematic debugging workflow enforces root cause investigation, pattern analysis, hypothesis testing, and implementation to ensure fixes target underlying problems rather than symptoms.

How do I debug flaky tests and production outages without treating symptoms?▼

Debug flaky tests and production outages by starting with Phase 1 root cause investigation, then pattern analysis, hypothesis testing, and implementation to locate the true trigger before fixing.

What's the best way to prevent bug regression after fixing a complex software issue?▼

The best way to prevent bug regression is applying defense-in-depth practices and root-cause tracing during implementation to reduce recurrence of complex software issues.

Can I use this systematic debugging approach for performance problems and integration issues?▼

Yes, this systematic debugging approach applies to any technical issue including performance problems, integration issues, test failures, and production bugs across software projects.

Why does fixing symptoms instead of root causes cause complex bug cascades?▼

Fixing symptoms instead of root causes causes complex bug cascades because the underlying problem remains unresolved, allowing the error to trigger further failures across the system.

Related Skills

Explore More Software Engineering Skills→
timequitytimequity
6

systematic-debugging

Enforce a four-phase root-cause investigation workflow before applying fixes to bugs and test failures.

Official
Advanced
aist-ai-sastaist-ai-sast

mcp-regression-fix

Diagnose MCP regression failures and implement durable fixes across test suites.

Official
Advanced
rileyhilliardrileyhilliard
127

systematic-debugging

Guide four-phase debugging to identify root causes before proposing fixes.

Community
Basic
sammy9322sammy9322

systematic-debugging

Investigate technical issues through a structured 4-phase root cause process.

Community
Advanced