debugging

Apply a four-phase Systematic Debugging framework to uncover root causes before patches.

10|2|Updated Mar 12, 2026

Search Tags:#debugging #troubleshooting #playbook #systematic #ci-cd #root-cause #chrome-devtools

Ready to run

npx skills add https://github.com/viktorbezdek/skillstack --skill debugging-viktorbezdek

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debugging
Source: https://github.com/viktorbezdek/skillstack/tree/main/debugging/skills/debugging
Command: npx skills add https://github.com/viktorbezdek/skillstack --skill debugging-viktorbezdek

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The systematic debugging approach helps engineers uncover root causes rather than applying symptom fixes, reducing rework and accelerating resolution.

Core Features & Use Cases

Systematic four-phase framework (Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, Implementation) applied to bugs across development, testing, and production.
Browser and CI/CD debugging toolkit, including DevTools workflows, performance profiling, and AI-assisted analysis.
Defense-in-depth validation to ensure fixes work across layers and environments.

Quick Start

Initiate the debugging workflow on any issue by following Phase 1 through Phase 4 to identify root causes and implement robust fixes.

Frequently Asked Questions about debugging

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

FAQPage Schema

What is a systematic debugging framework for uncovering root causes?▼

Systematic debugging is a four-phase framework—Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, and Implementation—that uncovers actual root causes before applying patches to prevent symptom fixes and reduce rework.

How do I troubleshoot CI/CD pipeline failures and production incidents?▼

Troubleshoot CI/CD pipeline failures and production incidents by applying a systematic debugging framework that leverages pattern analysis and performance profiling to identify root causes before implementing validated fixes.

How do I debug performance bottlenecks using Chrome DevTools workflows?▼

Debug performance bottlenecks using Chrome DevTools workflows by applying the systematic debugging framework's pattern analysis and hypothesis testing phases to isolate root causes before implementing fixes.

Does this systematic debugging approach work for both unit and integration failures?▼

Yes, this systematic debugging approach works for unit and integration failures, as well as production incidents and performance bottlenecks, applying root-cause investigation across all development and testing environments.

What is the best way to ensure software fixes work across different environments?▼

The best way to ensure fixes work across environments is defense-in-depth validation, which verifies that root-cause patches function correctly across multiple layers and environments before deployment.

Why should I investigate root causes before applying patches to bugs?▼

You should investigate root causes before applying patches because systematic debugging prevents symptom fixes, reducing rework and accelerating resolution by ensuring the underlying issue is actually resolved.