skills.rest
kamelmh
kamelmhCOMMUNITY
Explore all skills by this author →
GitHub

debugging-wizard

Analyze error messages, stack traces, and logs to isolate root causes.

Updated Aug 27, 2026
Search Tags:#debugging#troubleshooting#logs#root cause analysis#regression testing#bug isolation#stack traces
One-click install
npx skills add https://github.com/kamelmh/opencode-config --skill debugging-wizard-kamelmh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debugging-wizard
Source: https://github.com/kamelmh/opencode-config/tree/main/skills/debugging-wizard
Command: npx skills add https://github.com/kamelmh/opencode-config --skill debugging-wizard-kamelmh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps diagnose software failures by turning error messages, stack traces, and logs into a clear root-cause analysis. It is designed for situations where behavior is unexpected, crashes are intermittent, or prior fixes have not worked.

Core Features & Use Cases

  • Root Cause Analysis: Trace failures backward from symptoms to the exact point of failure.
  • Systematic Triage: Reproduce issues, isolate variables, and test one hypothesis at a time.
  • Debugging Guidance: Use common bug patterns, debugger commands, and proven strategies to narrow down the problem.
  • Regression Prevention: Recommend verification steps and regression tests after the fix.
  • Use Case: A service crashes after deployment, and you need to inspect the stack trace, compare recent changes, confirm the failing path, and propose a safe fix with a test.

Quick Start

Use the debugging-wizard skill to analyze this error, identify the root cause, and recommend the smallest verified fix with a regression test.

Frequently Asked Questions about debugging-wizard

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

FAQPage Schema
How do I find the root cause of a crash from a stack trace?▼

Root cause analysis from a stack trace involves tracing failures backward from symptoms to the exact point of failure. You analyze error messages and logs to isolate the failing path, then reproduce the issue stepwise to confirm the defect.

What is the best way to debug intermittent or hard-to-reproduce defects?▼

Debugging intermittent defects requires systematic triage by reproducing issues, isolating variables, and testing one hypothesis at a time. Collect evidence from logs and runtime environments to narrow down the unexpected behavior across the codebase.

How do I isolate variables when troubleshooting unexpected software behavior?▼

To isolate variables during troubleshooting, apply stepwise reproduction to test one hypothesis at a time. Compare recent changes against the expected behavior and collect evidence from logs to systematically narrow down the root cause.

Can I use this approach to debug regressions after a recent deployment?▼

Yes, debugging regressions after deployment works by analyzing new error messages and comparing recent changes to isolate the failing path. You reproduce the issue, confirm the failing code path, and propose a safe verified fix.

How do I prevent regressions after applying a bug fix?▼

To prevent regressions after a bug fix, implement regression testing and verification steps. Recommend specific regression tests that verify the fix and ensure the unexpected behavior or crash does not reoccur in the codebase.

Related Skills

Explore More Software Engineering Skills→
seb1nseb1n
147

Debugging

Diagnose software bugs by analyzing error messages, stack traces, and logs.

Community
Advanced
aimskraimskr

debug-specialist

Reproduce runtime bugs by collecting logs, traces, and environment context.

Official
Advanced
dhruvbaldawadhruvbaldawa
31

testing

Validate test coverage and add minimal edge-case tests for task files.

Community
Intermediate
bryonjacobbryonjacob

software-debugging

Breaks down bugs by applying hypothesis-driven analysis to identify root causes.

Community
Basic