skills.rest
wodeh
wodehCOMMUNITY
Explore all skills by this author →
GitHub

gstack-openclaw-investigate

Classify software bugs by pattern and produce a structured debug report.

Updated May 11, 2026
Search Tags:#debugging#investigation#code-analysis#hypothesis#root-cause#reproduction#debug-report
One-click install
npx skills add https://github.com/wodeh/gstack-kimi --skill gstack-openclaw-investigate-wodeh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gstack-openclaw-investigate
Source: https://github.com/wodeh/gstack-kimi/tree/main/openclaw/skills/gstack-openclaw-investigate
Command: npx skills add https://github.com/wodeh/gstack-kimi --skill gstack-openclaw-investigate-wodeh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging helps teams identify the true root cause of bugs before coding a fix, reducing rework and outages.

Core Features & Use Cases

  • Phase-based investigation: collect symptoms, read code paths, and reproduce deterministically.
  • Pattern analysis and hypothesis testing to classify issues and validate fixes.
  • Produce a structured debug report with symptom, root cause, fix, evidence, and status.

Quick Start

Run the five-phase debugging workflow to trace a bug from symptoms to a final debug report.

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?▼

Systematic root-cause debugging identifies the true cause of software bugs before coding a fix. You need it when reducing rework and outages by collecting symptoms, reading code paths, and reproducing issues deterministically.

How do I investigate a race condition or state corruption bug?▼

To investigate race conditions or state corruption, apply a Phase 2 pattern analysis to classify issues, read code paths, test hypotheses, and search for known issues and prior fixes to validate the root cause.

How do I reproduce a software bug deterministically for code analysis?▼

Reproduce a software bug deterministically by following a phase-based investigation workflow that collects symptoms and reads code paths to trace the issue from initial observation to a structured debug report.

What's the best way to generate a structured debug report?▼

The best way to generate a structured debug report is completing a five-phase debugging workflow that outputs symptom, root cause, fix, evidence, regression test, related notes, and a DONE status.

Does this debugging workflow work for configuration drift and stale cache issues?▼

Yes, this debugging workflow handles configuration drift and stale caches through Phase 2 pattern analysis, classifying these issues alongside nil propagation and integration failures to search for known issues and prior fixes.

Related Skills

Explore More Software Engineering Skills→
jk278jk278

debugging-assistant

Diagnose software bugs from stack traces and error logs.

Community
Advanced
chriswesttchriswestt

gstack-openclaw-investigate

Identify bug root causes through symptom collection, code path tracing, and deterministic reproduction.

Community
Advanced
fluxforgeaifluxforgeai
3

investigate

Perform hypothesis-driven root cause analysis and generate investigation reports.

Community
Advanced
JeremiahEllingtonJeremiahEllington

investigate

Diagnose root causes of bugs through structured investigation of symptoms and code paths.

Community
Advanced