debug

Debug errors through a five-step workflow with multi-layer verification.

Updated Aug 6, 2025
One-click install
npx skills add https://github.com/flosrn/.claude --skill debug-flosrn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/flosrn/.claude/tree/main/skills/workflow-debug
Command: npx skills add https://github.com/flosrn/.claude --skill debug-flosrn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill systematically debugs errors by analyzing the problem, finding solutions, proposing options, implementing fixes, and verifying them through multi-layer checks.

Core Features & Use Cases

  • Error Analysis: Reproduces errors, identifies root causes, and forms hypotheses.
  • Solution Discovery: Researches multiple potential fixes with pros and cons.
  • Automated & Interactive Modes: Can operate fully automatically or guide the user through the process.
  • Multi-Layer Verification: Ensures fixes are robust through static analysis, build checks, runtime execution, and user confirmation.
  • Use Case: When your API is returning a 500 error, you can use this Skill to automatically debug the issue, identify the cause, and apply a fix without manual intervention.

Quick Start

Debug an API returning 500 on POST.

Frequently Asked Questions about debug

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

FAQPage Schema
How do I systematically debug an API 500 error without manual intervention?

Systematic error debugging resolves API 500 errors by reproducing the issue, forming hypotheses, researching solutions, and applying fixes. It operates in automatic mode to handle the entire workflow without manual intervention.

What is the best way to find the root cause of a code error through troubleshooting?

Systematic error debugging finds the root cause of a code error through a 5-step workflow: analyzing the problem, discovering solutions, proposing options, implementing fixes, and verifying through static analysis and runtime execution.

Can I use interactive debugging to guide me through fixing complex errors?

Yes, interactive debugging can guide you through fixing complex errors step by step. It analyzes the problem, proposes multiple fix options with pros and cons, and asks for user confirmation before applying the resolution.

How do you verify an error resolution to ensure the fix is robust?

To verify an error resolution is robust, the debugging workflow performs multi-layer checks including static code analysis, build checks, runtime execution, and user confirmation to ensure the applied fix resolves the original issue.

What are the limitations of automatic error debugging for software verification?

Automatic error debugging requires structured analysis and hypothesis testing to function effectively. While it handles various error contexts automatically, complex unresolved issues may still need interactive mode for manual user confirmation during verification.