debug

Diagnose and fix failing tests, type errors, or runtime errors.

10|2|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/dixus/claudeframework --skill debug-dixus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/dixus/claudeframework/tree/main/.claude/skills/debug
Command: npx skills add https://github.com/dixus/claudeframework --skill debug-dixus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnoses and fixes a failing test, type error, or runtime error by guiding a structured debugging workflow that minimizes rewrites and unnecessary changes.

Core Features & Use Cases

  • Identify the exact failure point across typecheck, lint, and tests, and isolate the root cause.
  • Read project specifications (CLAUDE.md) to confirm verify commands and expected behavior, then apply a minimal fix and re-run checks.
  • Generate a concise report detailing root cause, files touched, and verification status, suitable for handoff to peers.

Quick Start

Invoke the debug skill when a test or build step fails and provide the error message, test name, or file path as the argument.

Frequently Asked Questions about debug

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

FAQPage Schema
How do I fix a failing test or runtime error without rewriting unrelated code?

To debug a failing test, this skill follows a structured workflow: reading project specifications to confirm verify commands, identifying the exact failure point, proposing a minimal fix, and re-running tests to confirm the resolution.

What is the best way to isolate the root cause of a build step failure?

Isolating a root cause involves reading project specifications to confirm expected behavior, identifying the exact failure point across typecheck and lint, applying a minimal fix, and generating a report detailing the root cause and files touched.

How do I debug a type error when a specific test fails in my CI pipeline?

Debugging a type error involves identifying the exact failure point across typecheck and lint, applying a minimal fix to resolve the error, and re-running tests to verify the correction without introducing unnecessary changes.

Do I need a CLAUDE.md file to diagnose and fix failing tests?

A CLAUDE.md file is needed because the debugging workflow reads it to confirm verify commands and expected behavior before proposing a minimal fix, ensuring the diagnosis aligns with project specifications.

Can I use this structured debugging workflow for CI-CD pipeline failures?

Yes, you can use this structured debugging workflow for CI-CD pipeline failures by applying it when a specific build step fails to quickly isolate root causes in your codebase and generate a handoff report.