debugger

Name: debugger
Availability: InStock
Author: buiphucminhtam

Guide structured debugging from symptom to root cause through triage and verification.

47|11|Updated Mar 6, 2026

Search Tags:#debugging #investigation #production #logs #triage #root-cause-analysis #regression-testing

Ready to run

npx skills add https://github.com/buiphucminhtam/forgewright --skill debugger-buiphucminhtam

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debugger
Source: https://github.com/buiphucminhtam/forgewright/tree/main/skills/debugger
Command: npx skills add https://github.com/buiphucminhtam/forgewright --skill debugger-buiphucminhtam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging helps teams quickly move from symptom to root cause by structuring investigation, logging, and verification workflows.

Core Features & Use Cases

Phase-based debugging workflow (Triage, Hypothesis, Investigation, Fix, Verification)
Structured evidence tracking and ReAct-style memory of steps
Guidance for regression testing and safe fixes across services

Quick Start

Provide a symptom description and I will begin Phase 1 triage to isolate the issue.

Frequently Asked Questions about debugger

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

FAQPage Schema

What is a systematic debugging workflow for moving from symptoms to root cause?▼

Systematic debugging isolates root causes by structuring investigation into triage, hypothesis, investigation, fix, and verification phases. It enforces rigorous evidence gathering and reproducibility to safely resolve complex production bugs and intermittent failures.

How do I triage production bugs and intermittent failures across complex codebases?▼

Triage production bugs by providing a symptom description to initiate structured evidence tracking. This approach isolates intermittent failures across complex codebases using ReAct-style memory to log steps and enforce reproducibility before applying fixes.

What's the best way to conduct root cause analysis for regression scenarios in production?▼

Root cause analysis for regressions requires structured evidence gathering and hypothesis testing. This systematic debugging approach guides teams through investigation workflows and enforces safe, minimal fixes to prevent further regressions across services.

Can I use this structured triage process for investigation and verification across multiple services?▼

Yes, the structured triage process applies to regression scenarios and complex codebases spanning multiple services. It provides guidance for verification workflows and regression testing to ensure safe, minimal fixes without introducing new issues.

Why does systematic debugging require rigorous evidence gathering and reproducibility?▼

Systematic debugging requires rigorous evidence gathering and reproducibility to prevent regressions during fixes. This structured approach ensures hypotheses are verified with concrete logs before applying minimal, safe changes across complex codebases.

When should I not use a phase-based debugging workflow for codebase investigations?▼

Phase-based debugging workflows are designed for complex codebases, production bugs, and regression scenarios. For trivial syntax errors or isolated single-component issues, a full structured triage and hypothesis process may be unnecessary overhead.