debugging

Guide teams through structured debugging protocols to identify root causes and verify fixes.

346|50|Updated Jan 17, 2026

Search Tags:#debugging #investigation #quality-assurance #triage #reproduction #root-cause-analysis

Ready to run

npx skills add https://github.com/liza-mas/liza --skill debugging-liza-mas

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debugging Protocol guides teams to systematically identify root causes and validate fixes, reducing guesswork and regression risk.

Core Features & Use Cases

Structured bug intake and qualification
Dual-path debugging: Fast Path and Normal Path
Rigorous verification, escalation, and post-mortem reflection
Facilitates reproducibility and stakeholder communication

Quick Start

Start by reading the Debugging Protocol and selecting the appropriate path for the current bug scenario.

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 structure debugging for reliable software fixes?▼

Structured debugging reduces guesswork and regression risk by systematically identifying root causes and validating fixes. It guides teams through dual-path triage, reproduction steps, and verification across local development, CI, and production environments.

How do I perform root cause analysis for bugs in a production environment?▼

Root cause analysis for production bugs uses structured debugging protocols to reproduce issues and verify fixes systematically. Teams apply fast-path triage or normal-path analysis, followed by structured escalation to ensure reliable incident resolution.

When do I need to use a structured debugging protocol instead of ad-hoc investigation?▼

A structured debugging protocol is needed when ad-hoc investigation risks regressions or fails to ensure reproducibility. It provides systematic bug qualification, dual-path triage, and escalation steps to maintain reliable fixes across local, CI, and production environments.

Can I use this debugging protocol for CI and local development environments?▼

Yes, the debugging protocol applies to local development, CI, and production environments. It systematically guides root cause identification, reproduction, and regression verification across all these software project environments using dual-path triage.

How do I start debugging a bug using the fast path or normal path?▼

Start debugging by reading the protocol and selecting the appropriate path for your bug scenario. Use the fast path for rapid triage or the normal path for rigorous analysis, reproduction, and verification to ensure reliable fixes and prevent regressions.

What are the limitations of relying on fast-path triage for bug investigation?▼

Fast-path triage accelerates initial resolution but lacks the rigorous reproduction and verification depth of normal-path analysis. For complex root cause identification, fast path may require escalation to normal path to prevent regressions and ensure reliable fixes.