skills.rest
voznik
voznikCOMMUNITY
Explore all skills by this author →
Website𝕏@vvoznikGitHub

systematic-debugging

Apply a four-phase root-cause debugging framework to resolve software defects.

Updated Aug 23, 2026
Search Tags:#debugging#troubleshooting#code-quality#root-cause#four-phase#bug-investigation
One-click install
npx skills add https://github.com/voznik/dotfiles --skill systematic-debugging-voznik
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/voznik/dotfiles/tree/main/.rulesync/skills/systematic-debugging
Command: npx skills add https://github.com/voznik/dotfiles --skill systematic-debugging-voznik

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Four-phase debugging methodology with root cause analysis to prevent patching symptoms and ensure fixes address the underlying cause.

Core Features & Use Cases

  • Phase-based investigation workflow: diagnosis, data gathering, hypothesis formation, and safe implementation.
  • Emphasizes tracing the issue to the original trigger and validating fixes before change.
  • Useful for test failures, runtime errors, intermittent issues, and regression debugging.

Quick Start

Identify the root cause, document it clearly, and implement a minimal fix that addresses the underlying issue.

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 symptoms?▼

Root-cause debugging traces the issue to the original trigger by applying a four-phase framework: diagnosis, data gathering, hypothesis formation, and safe implementation to ensure the underlying cause is fixed.

What is the best way to troubleshoot intermittent test failures and regressions?▼

Troubleshooting intermittent test failures requires documenting the root cause, reproducing the issue, analyzing data, and forming hypotheses before implementing minimal fixes and tracking results.

How do I systematically investigate runtime errors in my codebase?▼

Investigating runtime errors systematically involves a phase-based workflow that emphasizes tracing the issue to its original trigger and validating fixes before making changes.

Does root-cause debugging work for behavior troubleshooting across different systems?▼

Root-cause debugging applies to bug investigations, test failures, runtime errors, and behavior troubleshooting across various codebases and systems without requiring additional dependencies.

When should I avoid patching symptoms and use a four-phase debugging framework?▼

You should use a four-phase debugging framework when facing test failures, runtime errors, intermittent issues, or regression debugging to prevent patching symptoms and ensure fixes address the underlying cause.

Related Skills

Explore More Software Engineering Skills→
traylinxtraylinx
2

debugging-expert

Systematically debug software issues using structured workflows and diagnostic steps.

Official
Advanced
abzhawabzhaw

test-driven-development

Enforce a test-first workflow with failing tests before implementation.

Community
Intermediate
Donaldshen27Donaldshen27

systematic-debugging

Identify bug root causes through a four-phase systematic debugging framework.

Community
Advanced
valtterimelkkovaltterimelkko
1

systematic-debugging

Investigate root causes through a four-phase debugging framework before modifying code.

Community
Advanced