code-debug

Diagnose root causes of failing tests and bugs via a debugger subagent.

4|Updated Aug 8, 2026
One-click install
npx skills add https://github.com/alexeyshishin/as-skill --skill code-debug-alexeyshishin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-debug
Source: https://github.com/alexeyshishin/as-skill/tree/main/domains/code/skills/code-debug
Command: npx skills add https://github.com/alexeyshishin/as-skill --skill code-debug-alexeyshishin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a test fails or a build reports blocked, developers often patch symptoms blindly instead of finding the root cause. This Skill enforces a diagnose-first workflow that reproduces the issue, ladders hypotheses, and applies only evidence-backed minimal fixes. ## Core Features & Use Cases - Root Cause Diagnosis: Spawns a single debugger subagent that reproduces the failure and isolates the cause with evidence before touching code. - Hypothesis Laddering: Systematically works through candidate causes and returns the full chain when it cannot fix the issue outright. - Outcome Routing: Routes results by verdict — fixed issues go to code review, stuck cases surface the hypothesis ladder for user decision, and non-reproducible bugs request exact repro steps instead of guess-patching. - Use Case: A test suite fails after a feature build. Invoke the Skill with the failing test name, and it returns the root cause, supporting evidence, the minimal fix, and the re-run output. ## Quick Start Ask the AI to run /code-debug with the failing test name or error message to find the root cause and apply a minimal fix.

Frequently Asked Questions about code-debug

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

FAQPage Schema
How do I debug a failing test with an AI agent?▼

Invoke /code-debug with the failing test name or error text. It spawns one debugger subagent that reproduces the failure, ladders hypotheses, isolates the root cause with evidence, and applies a minimal fix before re-running the test.

What is root cause debugging versus patching symptoms?▼

Root cause debugging diagnoses the underlying defect through reproduction and evidence before changing code, while symptom patching modifies code blindly. This Skill enforces the diagnose-first approach and refuses to guess-patch when a bug cannot be reproduced.

When should I use code-debug instead of code-build?▼

Use code-debug when a test fails, a build returns blocked, or something stopped working. Use code-build for implementing features. The debug Skill sits between build and review in the development loop and does not design features.

What happens when a bug cannot be reproduced?▼

The debugger returns a cannot_reproduce verdict, and the Skill asks you for exact reproduction steps instead of guessing at a fix. This prevents blind patches that could introduce new defects.

What are the limitations of automated hypothesis-ladder debugging?▼

The debugger may return stuck or root_cause_found without a fix when evidence is inconclusive. In those cases it presents the full hypothesis chain so the user decides the fix or re-runs the build with the root cause as input.