skills.rest
cy-wali
cy-waliCOMMUNITY
Explore all skills by this author →
GitHub

debug

Guide structured debugging sessions to reproduce, isolate, diagnose, and fix bugs.

1|Updated Mar 19, 2026
Search Tags:#workflow#debugging#troubleshooting#logs#root-cause#reproduction#error-message
One-click install
npx skills add https://github.com/cy-wali/knowledge --skill debug-cy-wali
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/cy-wali/knowledge/tree/main/engineering/skills/debug
Command: npx skills add https://github.com/cy-wali/knowledge --skill debug-cy-wali

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Structured debugging sessions eliminate guesswork by guiding you through reproducibility, isolation, and root-cause diagnosis to fix issues efficiently.

Core Features & Use Cases

  • Structured workflow: reproduce, isolate, diagnose, and fix bugs with a repeatable process.
  • Incident scenarios: handles runtime errors, deployment regressions, flaky tests, and integration issues.
  • Guided outcomes: provides a concrete fix plan, validation steps, and prevention measures.

Quick Start

Provide the error message or stack trace to begin a structured debugging session.

Frequently Asked Questions about debug

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

FAQPage Schema
How do I find the root-cause of a runtime error using a structured debugging workflow?▼

A structured debugging workflow isolates the root-cause by guiding you through issue reproduction, log analysis, and error diagnosis to fix runtime errors efficiently.

What is the best way to reproduce and isolate flaky tests or deployment regressions?▼

To reproduce and isolate flaky tests or deployment regressions, use a structured debugging session to capture error messages, define reproduction steps, and analyze relevant logs.

Can I use this debugging process for integration issues across different software stacks?▼

Yes, this debugging process applies to integration issues across software stacks, handling problems triggered by unexpected behavior, deployment changes, or configuration errors.

How do I start troubleshooting an issue when I only have an error message and stack trace?▼

Troubleshooting begins by providing the error message or stack trace to initiate a structured session that yields a concrete fix plan, validation steps, and preventive tests.

What steps should I follow to diagnose and fix unexpected behavior in my code?▼

To diagnose and fix unexpected behavior, follow a repeatable process of reproducing the issue, isolating variables, performing root-cause analysis, and proposing validated fixes.

When should I use a structured debugging session instead of ad-hoc troubleshooting?▼

Use a structured debugging session instead of ad-hoc troubleshooting when you need repeatable isolation strategies and guided outcomes to eliminate guesswork for complex bugs.

Related Skills

Explore More Software Engineering Skills→
FoundationForgeFoundationForge

debug

Run structured debugging sessions to reproduce, isolate, and diagnose software errors.

Official
Intermediate
korchasakorchasa
3

flow-fix-by-benchmarks

Run benchmarks to identify skill failure root causes and propose fixes.

Community
Advanced
g-zenrg-zenr

troubleshoot

Diagnose runtime and production issues by analyzing logs and errors.

Community
Intermediate
JansenAnalyticsJansenAnalytics
5

error-monitor

Monitor application logs and stderr to detect errors, crashes, and exceptions.

Community
Intermediate