skills.rest
Design-System-ET
Design-System-ETOFFICIAL
Explore all skills by this author →
GitHub

debugging-wizard

Parse error messages and stack traces to isolate root causes.

Updated Jun 16, 2026
Search Tags:#debugging#troubleshooting#root cause analysis#stack trace#git bisect#error investigation
One-click install
npx skills add https://github.com/Design-System-ET/genexus-dev-opencode --skill debugging-wizard-design-system-et
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debugging-wizard
Source: https://github.com/Design-System-ET/genexus-dev-opencode/tree/main/skills/debugging-wizard
Command: npx skills add https://github.com/Design-System-ET/genexus-dev-opencode --skill debugging-wizard-design-system-et

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill eliminates the guesswork and frustration of debugging by providing a structured, hypothesis-driven framework to isolate root causes in any codebase.

Core Features & Use Cases

  • Systematic Methodology: Guides you through reproduction, isolation, hypothesis testing, and verification to prevent the "fix one, break two" cycle.
  • Cross-Language Support: Provides specific commands and strategies for Python, JavaScript/TypeScript, and Go debugging.
  • Regression Hunting: Includes automated workflows for Git bisect to identify exactly when a bug was introduced.

Quick Start

Use the debugging-wizard to analyze the provided stack trace and suggest a systematic plan to isolate the root cause of the current exception.

Frequently Asked Questions about debugging-wizard

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

FAQPage Schema
How do I systematically isolate the root cause of a complex bug?▼

To isolate a root cause, use a structured methodology for reproduction, isolation, and hypothesis testing to prevent the fix one, break two cycle. This approach guides you through verifying failure points before applying fixes.

How do I find when a regression was introduced using git bisect?▼

Git bisect identifies when a regression was introduced through automated workflows that systematically narrow down commits. This regression hunting process isolates the exact code change causing the failure.

Can I use this systematic debugging methodology for Python, JavaScript, and Go codebases?▼

Yes, this debugging methodology provides specific commands and strategies for Python, JavaScript/TypeScript, and Go codebases. It applies cross-language support to parse stack traces and identify failure points.

What is the best way to analyze error messages and stack traces for failure points?▼

Analyzing error messages and stack traces requires a hypothesis-driven methodology to identify failure points accurately. This systematic approach parses diagnostic data to verify the exact source of exceptions.

Does this approach work for complex bug isolation requiring diagnostic instrumentation?▼

Yes, this approach satisfies requirements for structured debugging workflows, diagnostic instrumentation, and verified fix implementation. It applies specifically to codebases requiring complex bug isolation and root cause analysis.

Related Skills

Explore More Software Engineering Skills→
0xHarbs0xHarbs
1

debug

Diagnose failures by applying hypothesis-driven root-cause analysis to test outputs, stack traces, and CI logs.

Community
Advanced
bostonaholicbostonaholic
8

test-driven-bug-fix

Reproduce, isolate, fix, and verify software defects using test-driven methodology.

Community
Advanced
baphledbaphled
1

git-advanced

Perform advanced Git operations including rebase, bisect, cherry-pick, and reflog recovery.

Community
Intermediate
flutterflutter
2.8k

dart-fix-runtime-errors

Identify and resolve Dart static analysis errors and runtime exceptions.

Official
Intermediate