gh:debug

Trace bugs from trigger to symptom and validate root causes.

2|1|Updated Apr 17, 2026

Search Tags:#debugging #troubleshooting #memory #bugs #root-cause #causal-chain

Ready to run

npx skills add https://github.com/wangrenzhu-ola/GaleHarnessCodingCLI --skill gh-debug-wangrenzhu-ola

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gh:debug
Source: https://github.com/wangrenzhu-ola/GaleHarnessCodingCLI/tree/main/plugins/galeharness-cli/skills/gh-debug
Command: npx skills add https://github.com/wangrenzhu-ola/GaleHarnessCodingCLI --skill gh-debug-wangrenzhu-ola

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps engineers diagnose bugs by constructing a complete causal chain from trigger to symptom, ensuring fixes are evidence-based rather than symptom-driven.

Core Features & Use Cases

Phase-driven debugging that guides investigation from triage to handoff with guardrails.
Gale Memory integration to recall task context and prior solutions to accelerate root-cause analysis.
Structured handoffs including root cause, proposed fixes, tests, and prevention notes to accelerate remediation.

Quick Start

Describe the bug you want to investigate and the skill will start a structured, phase-based debugging workflow.

Frequently Asked Questions about gh:debug

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

FAQPage Schema

How do I systematically debug code to find the root cause of an error?▼

To debug systematically, you trace a full causal chain from the trigger to the symptom, validating the root cause with evidence before applying a fix. This approach ensures your debugging is evidence-based rather than driven by surface symptoms.

What is a causal chain in software debugging and troubleshooting?▼

A causal chain in debugging is the complete sequence of events from the initial trigger to the final symptom. Building this chain ensures you identify the true root cause of bugs instead of patching isolated failures.

How do I start a structured investigation for failing tests in my codebase?▼

Start a structured investigation for failing tests by entering a phase-driven debugging workflow that guides you from initial triage to handoff. Describe the test failure to begin building the causal chain.

Can I use memory context to recall prior solutions when diagnosing bugs?▼

Yes, you can use memory context to recall task context and prior solutions during bug diagnosis. This integration accelerates root-cause analysis by applying historical evidence to the current investigation.

Does phase-driven debugging work for issue-tracker investigations across different environments?▼

Yes, phase-driven debugging works for issue-tracker investigations across codebases, teams, and environments. It provides guardrails to navigate from triage to a validated fix regardless of the environment context.

What's the best way to hand off an unresolved bug to another engineer?▼

The best way to hand off an unresolved bug is to provide a structured report including the root cause, proposed fixes, tests, and prevention notes. This structured handoff accelerates remediation for the receiving engineer.