dev-debug

Diagnose runtime errors and build failures through a 9-phase debugging workflow.

Updated Jan 1, 2026

Search Tags:#debugging #root-cause-analysis #bug-investigation #runtime-errors #build-failures #investigation-workflow

Ready to run

npx skills add https://github.com/AirMile/claude-config --skill dev-debug-airmile

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dev-debug
Source: https://github.com/AirMile/claude-config/tree/main/skills/dev-debug
Command: npx skills add https://github.com/AirMile/claude-config --skill dev-debug-airmile

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a systematic, multi-phase debugging workflow to identify root causes of runtime errors, build failures, and unexpected behavior, enabling fast and reliable fixes across projects.

Core Features & Use Cases

9-phase debugging process: context → intake → investigate → analyze → research → fix plans → select → implement → verify.
Inline investigation workflow: isolates debugging to prevent cross-project contamination.
Actionable plan generation: root-cause analysis, change proposals, and verification steps.

Quick Start

Describe the issue succinctly to trigger the inline debugging workflow.

Frequently Asked Questions about dev-debug

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

FAQPage Schema

How do I find the root cause of a runtime error or build failure?▼

To find the root cause of a runtime error or build failure, follow a structured 9-phase debugging workflow that loads project context, analyzes stack traces and logs, and generates actionable fix proposals.

What is the best way to investigate logic bugs and performance problems across a codebase?▼

The best way to investigate logic bugs and performance problems is using a multi-pass analysis framework that isolates debugging to prevent cross-project contamination while diagnosing codebase integration failures.

How do I debug an issue when I only have a short description of the unexpected behavior?▼

You can debug unexpected behavior from a short description by triggering an inline investigation workflow that gathers context from project files, stack traces, and logs to perform multi-pass root-cause analysis.

Can I use this structured debugging workflow to diagnose integration failures in any project?▼

Yes, you can use this structured debugging workflow to diagnose integration failures in any project by applying its context loading, problem intake, and multi-pass analysis phases across different codebases.

Does root-cause analysis for runtime errors require specific dependencies or environment setup?▼

No, root-cause analysis for runtime errors requires no specific dependencies or environment setup, allowing you to directly gather context from project files, stack traces, and logs to investigate issues.

What are the limitations of using a structured investigation workflow for bug investigation?▼

A limitation of this structured investigation workflow is that it only provides root-cause analysis, change proposals, and verification plans, meaning you must still implement and validate the actual code fixes yourself.