debugger

Diagnose code errors by collecting context and guiding focused troubleshooting steps.

12|2|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/hartphoenix/weft --skill debugger-hartphoenix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debugger
Source: https://github.com/hartphoenix/weft/tree/main/.claude/skills/debugger
Command: npx skills add https://github.com/hartphoenix/weft --skill debugger-hartphoenix

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill assists users in diagnosing and fixing bugs by guiding error analysis, collecting context, and teaching error-reading skills.

Core Features & Use Cases

  • Error Context Collection: Gathers full error messages and stack traces to facilitate quick diagnosis.
  • Hypotheses Prompting: Encourages users to articulate their assumptions to narrow down issues.
  • Layer and Dependency Analysis: Identifies the problem layer (syntax, logic, environment) and maps dependencies to locate root causes.
  • Rescoping Guidance: Helps users refine their problem scope for efficient troubleshooting.
  • Iterative Debugging: Supports incremental troubleshooting and repeated hypothesis testing.

Quick Start

When encountering an error, provide the full error message and context, then follow the step-by-step guidance to analyze and resolve the issue.

Frequently Asked Questions about debugger

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

FAQPage Schema
How do I diagnose a code error using a stack trace?

You can fix bugs by providing the full error message and context, then following step-by-step guidance to classify error layers, articulate assumptions, and iteratively test hypotheses until the root cause is resolved.

What is the best way to troubleshoot environment versus logic errors?

The best way to troubleshoot environment versus logic errors is by classifying the error layer and mapping dependencies. This isolates whether the root cause originates from syntax, logic, or environment configurations.

How do I narrow down the scope when bug troubleshooting fails?

To narrow down the scope when bug troubleshooting fails, use rescoping guidance to refine the problem boundaries and prompt new hypotheses. This supports iterative testing to isolate the specific failing component.

Can I use this approach to fix syntax errors without deep technical knowledge?

Yes, you can fix syntax errors without deep technical knowledge. The system teaches error-reading skills by guiding context collection and providing step-by-step analysis to resolve the issue efficiently.

Why does iterative debugging help with error diagnosis?

Iterative debugging helps with error diagnosis by supporting incremental troubleshooting and repeated hypothesis testing. This methodical process ensures you systematically eliminate variables to locate the exact root cause.