debugging

Guide structured debugging through framing, reproduction, instrumentation, and root-cause analysis.

Updated Aug 27, 2026

Search Tags:#debugging #verification #protocol #observability #instrumentation #reproducibility #root-cause analysis

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debugging ensures certainty before code changes by providing a disciplined protocol that reduces guesswork and regression risk.

Core Features & Use Cases

Structured Bug Intake: captures context, reproduction steps, and observations to drive deterministic resolution.
Dual-path strategy: Fast Path for obvious issues and Normal Path for complex bugs with escalation guidelines.
Observability and instrumentation guidelines: guidance to instrument logs, timestamps, and state tracking.
Root Cause and Resolution framework: a gate-based approach to identify root cause and verify fixes.

Quick Start

Run the debugging protocol on a failing task to isolate the trigger, instrument logs, and validate hypotheses.

Frequently Asked Questions about debugging

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

FAQPage Schema

What is a deterministic debugging workflow for root-cause analysis?▼

A disciplined debugging protocol reduces guesswork by enforcing structured bug intake, reproduction, and root-cause analysis. It ensures certainty before code changes by capturing context and validating hypotheses across local, CI, and multi-agent contexts.

How do I reproduce a bug and isolate the trigger in a CI environment?▼

Isolate a bug trigger by running a structured intake to capture reproduction steps and observations. Then select a fast or normal path strategy and apply observability guidelines to instrument logs and track state across CI environments.

What is the best way to instrument logs for reproducibility during bug resolution?▼

Instrument logs for reproducibility by following observability guidelines that enforce explicit timestamps and state tracking. This instrumentation captures the exact conditions needed to validate hypotheses and perform root-cause analysis.

When do I need a gate-based approach for root-cause analysis and regression checks?▼

Use a gate-based approach for root-cause analysis when resolving complex bugs to ensure certainty. This framework enforces explicit verification and regression checks, validating that the identified root cause and subsequent fixes are correct and safe.

Does this debugging protocol work for multi-agent contexts and local environments?▼

Yes, the debugging protocol works across local, CI, and multi-agent contexts. It provides a dual-path strategy with escalation guidelines, enabling practitioners to apply structured bug intake and instrumentation consistently regardless of the environment.