One-click install
npx skills add https://github.com/elianiva/dotfiles --skill debugging-elianiva
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debugging
Source: https://github.com/elianiva/dotfiles/tree/main/agents/skills/debugging
Command: npx skills add https://github.com/elianiva/dotfiles --skill debugging-elianiva

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debugging across codebases is often time-consuming and error-prone. This skill provides a disciplined, four-phase framework to systematically investigate, analyze, hypothesize, and implement fixes based on root-cause evidence.

Core Features & Use Cases

  • Structured investigation: Phase-driven approach reduces guesswork and rework.
  • Pattern analysis & hypothesis testing: Helps identify root causes efficiently across modules.
  • Safe implementation guidance: Emphasizes minimal, verifiable changes with clear verification steps.

Quick Start

Reproduce the issue, then apply Phase 1 (Root Cause Investigation) to gather evidence before proposing any fixes.

Frequently Asked Questions about debugging

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

FAQPage Schema
What is the best way to find the root cause of a software bug instead of just patching symptoms?

Root cause investigation involves reproducing the issue and gathering evidence before proposing fixes. This structured approach applies pattern analysis and hypothesis testing to accurately diagnose software bugs rather than guessing at symptoms.

How do I debug production bugs and performance problems systematically?

Debugging production bugs and performance problems systematically requires a four-phase framework: root-cause investigation, pattern analysis, hypothesis testing, and controlled implementation with evidence-based validation to ensure verifiable fixes.

Can I use this debugging approach for integration faults and test failures in complex codebases?

Yes, this debugging approach supports diagnosing integration faults and test failures across projects of varying complexity. The phase-driven methodology scales from isolated test failures to complex cross-module integration issues by enforcing evidence-based validation.

How to fix software bugs safely without introducing regressions?

Fixing software bugs safely requires controlled implementation guidance that emphasizes minimal, verifiable changes. After root-cause investigation and hypothesis testing, you apply changes with clear verification steps to prevent regressions and ensure stability.

What's the best way to trace root causes in software engineering instead of trial and error?

Root-cause tracing replaces trial and error with a disciplined, phase-driven framework. By systematically investigating evidence, analyzing failure patterns, and testing hypotheses, you identify the exact origin of code faults efficiently before implementing any changes.