debugging

Guides debugging workflows from triage to verification with structured decision points.

8|5|Updated Dec 30, 2025
One-click install
npx skills add https://github.com/axiomantic/spellbook --skill debugging-axiomantic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debugging
Source: https://github.com/axiomantic/spellbook/tree/main/skills/debugging
Command: npx skills add https://github.com/axiomantic/spellbook --skill debugging-axiomantic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debugging complex software systems often involves scattered notes, inconsistent practices, and delayed verification. This Skill provides a structured, repeatable process to triage symptoms, choose the right methodology, execute fixes, and verify outcomes with safeguards like the 3-fix rule.

Core Features & Use Cases

  • Triage and symptom classification: Quickly describe symptoms and determine reproducibility and impact.
  • Methodology selection: Choose between scientific and systematic approaches, or opt for direct fixes when appropriate.
  • Execution and verification: Run guided troubleshooting steps and automatically verify outcomes after each fix.
  • CI and environment analysis: Distinguish between local and CI failures and document environment differences.
  • Guardrails and governance: Enforce the 3-fix rule and escalation paths for architectural concerns.

Quick Start

Initiate a new debugging session by describing the symptom, then follow prompts to triage, select a methodology, and verify results.

Frequently Asked Questions about debugging

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

FAQPage Schema
How do I find a software bug root cause fast when symptoms are scattered?

Root-cause analysis for software bugs requires structured triage to classify symptoms and determine reproducibility. This Skill guides hypothesis-driven investigation to systematically identify root causes rather than applying unverified patches.

What is the 3-fix rule in debugging and when does it escalate?

The 3-fix rule in debugging limits repeated unsuccessful fix attempts before requiring escalation. This Skill enforces this guardrail by triggering structured decision points and architectural escalation paths after three failed verification checks.

How do I debug CI failures versus local environment differences?

Debugging CI versus local failures involves analyzing environment differences and distinguishing between local and CI failures. This Skill guides environment analysis to document discrepancies and triage whether failures are environment-specific or systemic.

What's the best way to verify a bug fix and prevent regressions?

Verifying a bug fix to prevent regressions requires strict outcome verification after each troubleshooting step. This Skill implements automated verification checks and structured decision points to ensure fixes resolve symptoms without introducing new issues.

When should I use scientific debugging versus systematic methods?

Scientific debugging uses hypothesis-driven investigation, while systematic methods follow structured troubleshooting steps. This Skill helps you choose between these approaches or opt for direct fixes when appropriate, based on symptom triage and impact classification.

Does this debugging workflow work without external dependencies?

This debugging workflow operates without external dependencies, using structured decision points and verification rules. It supports both automated and human-in-the-loop triage, making it suitable for any software engineering environment without prerequisite tools.