gstack-openclaw-investigate

Analyze software bugs through a five-phase root-cause investigation workflow.

1|Updated May 27, 2026

Search Tags:#debugging #code-analysis #reproduction #root-cause-analysis #stack-trace #bug-investigation

Ready to run

npx skills add https://github.com/mi179/claude-skills --skill gstack-openclaw-investigate-mi179

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gstack-openclaw-investigate
Source: https://github.com/mi179/claude-skills/tree/main/user/gstack/openclaw/skills/gstack-openclaw-investigate
Command: npx skills add https://github.com/mi179/claude-skills --skill gstack-openclaw-investigate-mi179

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides engineers to perform structured root-cause analysis for software bugs, preventing symptom-driven fixes and decreasing mean time to resolution.

Core Features & Use Cases

Phase-driven investigation: Follows a five-phase process (gather symptoms, read code, check changes, reproduce, and memory check) to surface root causes.
Pattern analysis & hypothesis testing: Classifies failures (race, nil propagation, state corruption, integration, configuration drift) and tests hypotheses with evidence.
Verification & reporting: Produces a structured debug report detailing symptom, root cause, fix, evidence, and regression tests for traceability.

Quick Start

Follow the five-phase debugging workflow to capture symptoms, hypothesize root causes, test hypotheses, implement fixes, and verify results.

Frequently Asked Questions about gstack-openclaw-investigate

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

FAQPage Schema

What is systematic root-cause debugging and when do I need it?▼

Root-cause debugging analyzes software bugs to identify underlying causes before fixing. It is needed when handling error messages, stack traces, and reproduction steps across complex code paths to prevent symptom-driven fixes.

How do I investigate a software bug using a structured debugging workflow?▼

Investigate a software bug by following a five-phase workflow: gather symptoms, read code, check changes, reproduce the issue, and perform memory checks. This structured process surfaces root causes through evidence gathering and pattern analysis.

Does this root-cause analysis approach work for race conditions and state corruption?▼

Yes, root-cause analysis handles race conditions and state corruption by classifying failures into patterns like nil propagation, state corruption, and integration issues. It tests hypotheses with evidence to verify the failure mechanism.

What is the best way to document a bug investigation and fix?▼

The best way to document a bug investigation is producing a structured debug report. This report details the symptom, root cause, implemented fix, gathered evidence, and regression tests for complete traceability.

Why should I use a structured debugging workflow instead of applying immediate fixes?▼

Use a structured debugging workflow instead of immediate fixes to decrease mean time to resolution. It prevents symptom-driven fixes by enforcing evidence gathering, pattern analysis, and hypothesis testing before implementation.