debug

Name: debug
Availability: InStock
Author: sun2443

Turn vague failures into a structured debug report with reproduction, root cause, and fix.

Updated Apr 8, 2026

Search Tags:#debugging #root cause analysis #stack trace #incident response #reproduction steps #production deploy

Ready to run

npx skills add https://github.com/sun2443/designer-skills --skill debug-sun2443

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/sun2443/designer-skills/tree/main/engineering/skills/debug
Command: npx skills add https://github.com/sun2443/designer-skills --skill debug-sun2443

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps when software behavior is confusing or inconsistent so you can reproduce the issue, isolate the failing component, diagnose the real root cause, and apply a safe fix without guessing.

Core Features & Use Cases

Structured debugging workflow: Reproduce, isolate, diagnose, and fix in a consistent sequence.
Root-cause oriented reporting: Produces a debug report with expected vs. actual, reproduction steps, root cause, fix, and prevention.
Context-aware assistance: Leverages available connectors (e.g., monitoring, source control, project tracker) to correlate logs, deploys, commits, and related tickets.

Quick Start

Run the /debug command with the exact error message or a short description of the problem so you receive a structured debug report.

Frequently Asked Questions about debug

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

FAQPage Schema

How do I debug production issues after a deploy using a stack trace?▼

You debug a stack trace by providing the exact error text to generate a structured workflow that reproduces, isolates, diagnoses, and fixes the production issue. It correlates connected logs and deploys to pinpoint the root cause safely.

What is the best way to find the root cause of environment-specific behavior differences?▼

Finding the root cause of environment-specific behavior differences requires a systematic debugging workflow. By providing the concrete failure report, you receive a structured debug report detailing reproduction steps, root cause, fix, and prevention.

How do I write reproduction steps for a vague software failure?▼

Writing reproduction steps for a vague software failure involves inputting the exact problem statement into a systematic troubleshooting workflow. This transforms the vague failure into a structured debug report containing explicit reproduction steps, root cause, and fix.

Can I use incident response logs and tickets to isolate a failing component?▼

Yes, you can use incident response logs and tickets to isolate a failing component. The debugging workflow leverages available connectors for project tracking and source control to correlate deploys, commits, and logs directly within the diagnostic report.

Does this debugging workflow require specific monitoring tools to diagnose a regression?▼

No, diagnosing a regression does not require specific monitoring tools, although connectors for logs and source control are leveraged if available. You only need to provide the exact problem statement or error text to initiate the troubleshooting sequence.