debug

Diagnose software issues by guiding a reproducible debugging workflow for error messages.

4|4|Updated Dec 15, 2024
One-click install
npx skills add https://github.com/adrianliechti/wingman-chat --skill debug-adrianliechti
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/adrianliechti/wingman-chat/tree/main/skills/engineering/debug
Command: npx skills add https://github.com/adrianliechti/wingman-chat --skill debug-adrianliechti

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Structured debugging sessions help teams quickly reproduce, isolate, diagnose, and fix issues raised by errors or unexpected behavior. It provides a repeatable framework to capture the exact reproduction steps, identify the faulty component, and verify the fix before deployment.

Core Features & Use Cases

  • Stepwise framework: REPRODUCE, ISOLATE, DIAGNOSE, FIX to guide the investigation.
  • Clear input prompts: error messages, stack traces, or divergent behavior to pin down scope.
  • Outputs and guardrails: actionable root-cause analysis, recommended fixes, test suggestions, and remediation steps.
  • Use in development, staging, or production deployments to reduce time-to-resolution and improve reliability.

Quick Start

Start a structured debugging session by providing the error message or stack trace and relevant context, then follow the four-step protocol to reproduce, isolate, diagnose, and fix the issue.

Frequently Asked Questions about debug

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

FAQPage Schema
How do I debug an error message using a structured workflow?

A structured debugging workflow guides you through reproducing the error, isolating the faulty component, diagnosing the root cause, and applying a verified fix. This repeatable framework reduces time-to-resolution and prevents regression.

What is the best way to find the root cause of a stack trace?

Finding the root cause of a stack trace involves a stepwise framework to reproduce the issue and isolate the faulty component. This systematic diagnosis outputs actionable root-cause analysis and recommended fixes to resolve the error.

Can I use structured troubleshooting for production environment issues?

Yes, structured troubleshooting applies to development, staging, and production environments. It provides a repeatable framework to capture exact reproduction steps, diagnose unexpected behavior, and verify the remediation steps before deployment.

How do I prevent regression when fixing unexpected software behavior?

To prevent regression when fixing unexpected software behavior, validate your recommended fixes with specific test suggestions. A structured debugging workflow requires generating validation tests as a final verification step after diagnosing the root cause.

What do I need to start diagnosing an error or unexpected behavior?

To start diagnosing an error or unexpected behavior, you need to provide the specific error message or stack trace along with relevant context. This input prompts the investigation to pin down the scope and guide the reproduction steps.