debug-assist

Classify error messages and stack traces into root-cause hypotheses with verification steps.

3|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/t6adev/claude-code-tools --skill debug-assist-t6adev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug-assist
Source: https://github.com/t6adev/claude-code-tools/tree/main/tools/skills/code/debug-assist
Command: npx skills add https://github.com/t6adev/claude-code-tools --skill debug-assist-t6adev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps developers diagnose error messages and stack traces by producing concise root-cause hypotheses and concrete repair plans.

Core Features & Use Cases

  • Classifies error types (runtime, type, lint, test, environment, and build) from input.
  • Identifies related files and context to narrow down root causes.
  • Proposes up to three actionable hypotheses with verification steps and concrete fixes.

Quick Start

エラーメッセージまたはスタックトレースを貼り付けてください、原因仮説と修正方針を返します。

Frequently Asked Questions about debug-assist

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

FAQPage Schema
How do I diagnose a JavaScript stack trace to find the root cause?

TypeScript type errors are classified by analyzing the error message and related files to generate root-cause hypotheses. You receive up to three actionable hypotheses with verification steps and non-destructive repair recommendations.

What is the best way to troubleshoot environment and build errors in TypeScript?

Troubleshooting environment and build errors involves classifying the error and reading related context to form root-cause hypotheses. It yields up to three targeted hypotheses with concrete verification steps and non-destructive repair plans.

Can I use this to diagnose runtime and test errors in JavaScript?

Yes, you can diagnose runtime and test errors by inputting the error message or stack trace. The system identifies related files and context to provide up to three root-cause hypotheses with actionable verification steps.

How do I start root-cause analysis from a stack trace?

To start root-cause analysis, paste an error message or stack trace. The system classifies the error, identifies related files, and proposes up to three actionable hypotheses with concrete verification steps and non-destructive recommendations.

What types of errors can be diagnosed from a stack trace?

Runtime, type, lint, test, environment, and build errors can be diagnosed from a stack trace. The system classifies the error type and reads related files to generate up to three root-cause hypotheses with verification steps.