debug

Diagnose build, test, and runtime failures to identify root causes.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/anionzo/skill --skill debug-anionzo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/anionzo/skill/tree/main/skills/debug
Command: npx skills add https://github.com/anionzo/skill --skill debug-anionzo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Systematic debugging to identify root causes for blocked workers, test failures, build errors, runtime crashes, and integration issues. It can be invoked standalone or by other skills to review failures and spawn debugging workflows. It references historical patterns to avoid re-solving known issues and records learnings for future reuse.

Core Features & Use Cases

  • Phase-based debugging process (Phase 0 to Phase 4) to guide root-cause analysis.
  • Cross-component diagnostics, and integration with Agent Mail for communication and escalation.
  • Repro and root-cause capture, with documented learnings and optional extraction.

Quick Start

Initiate a debugging session for a failure and follow the four-phase process to reach a verified fix.

Frequently Asked Questions about debug

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

FAQPage Schema
How do I find the root cause of test failures and build errors?

To find the root cause of test failures and build errors, apply a phase-based debugging process that performs cross-component diagnostics and references historical patterns to identify verified fixes.

What is a phase-based debugging process for runtime crashes?

A phase-based debugging process for runtime crashes guides root-cause analysis through structured phases, ensuring cross-component analysis, safe escalation, and documented learnings to prevent recurrence.

How do I debug integration issues across multiple components?

Debug integration issues by applying cross-component diagnostics that analyze failures across builds, tests, and runtimes, using Agent Mail for communication and safe escalation.

Can I automate debugging workflows for blocked workers from other skills?

Yes, you can automate debugging for blocked workers by invoking the debugging skill standalone or from other skills to review failures, spawn debugging workflows, and capture documented learnings.

What's the best way to prevent recurring incidents during software debugging?

The best way to prevent recurring incidents is to capture root causes and record documented learnings during debugging, extracting repeatable patterns for future reference to avoid re-solving known issues.

Why do I need historical references when diagnosing runtime crashes?

Historical references are needed when diagnosing runtime crashes to avoid re-solving known issues, applying previously documented learnings and repeatable patterns to reach a verified fix faster.