debugging

Diagnose bugs by tracing root causes through a six-phase debugging workflow.

Updated Jan 23, 2026
One-click install
npx skills add https://github.com/Veraticus/gambit --skill debugging-veraticus
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debugging
Source: https://github.com/Veraticus/gambit/tree/main/skills/debugging
Command: npx skills add https://github.com/Veraticus/gambit --skill debugging-veraticus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineers systematically diagnose bugs and failures by tracing root causes with evidence, reducing guesswork and regression risk.

Core Features & Use Cases

  • Phase-driven debugging workflow with enforced root-cause analysis
  • Tool-assisted investigation using WebSearch, Explore, and test automation
  • RED-GREEN cycle for regression testing via gambit:tdd and gambit:verify
  • Full-suite verification and documentation of findings after fixes

Quick Start

Start by creating a Bug Task with reproduction steps, then proceed through the SIX phases using Gambit commands and agents as described in the SKILL.

Frequently Asked Questions about debugging

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

FAQPage Schema
What is systematic root cause analysis for diagnosing software bugs?▼

The debugging workflow enforces root cause analysis through a six-phase process: creating a bug task with reproduction steps, investigating with tool-assisted search, running RED-GREEN regression cycles, and verifying fixes across the full test suite.

How do I trace a code investigation from bug reproduction to a verified fix?▼

You create a bug task with reproduction steps, use tool-assisted investigation to trace root causes with evidence, apply RED-GREEN regression cycles, and execute full-suite verification to ensure the fix resolves the issue without regressions.

Does this debugging workflow integrate with test-driven development cycles?▼

Yes, the debugging workflow integrates with test-driven development by enforcing RED-GREEN cycles via integrated gambit agents, requiring you to write failing regression tests before applying fixes, then verifying them with passing tests and full-suite checks.

Can I use this systematic bug diagnosis approach for any software engineering task?▼

You can use this systematic bug diagnosis approach for any software engineering task involving failure tracing and root cause analysis, as it enforces reproducibility, tool-assisted investigation, regression testing, and full-suite verification across general debugging tasks.

Why should I use evidence-based bug diagnosis instead of ad-hoc debugging?▼

Evidence-based bug diagnosis reduces guesswork and regression risk by enforcing a phase-driven workflow with tool-assisted investigation and full-suite verification, ensuring fixes are validated through RED-GREEN regression cycles rather than untested assumptions.