gstack-openclaw-investigate

Diagnoses bugs through root cause investigation, hypothesis testing, and verified fixes with regression tests.

Updated Aug 9, 2026
One-click install
npx skills add https://github.com/raghavbadhwar/rstack --skill gstack-openclaw-investigate-raghavbadhwar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gstack-openclaw-investigate
Source: https://github.com/raghavbadhwar/rstack/tree/main/openclaw/skills/gstack-openclaw-investigate
Command: npx skills add https://github.com/raghavbadhwar/rstack --skill gstack-openclaw-investigate-raghavbadhwar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Debugging often devolves into guessing and symptom-patching, which creates whack-a-mole bugs and wasted effort. This Skill enforces a disciplined five-phase workflow that finds the actual root cause before any fix is written, then proves the fix works with a regression test. ## Core Features & Use Cases - Structured Root Cause Investigation: Collects symptoms, traces code paths, checks recent git history, and reproduces the bug before forming any hypothesis. - Pattern Matching & Hypothesis Testing: Matches bugs against known patterns (race conditions, null propagation, state corruption, integration failures, config drift, stale caches) and enforces a 3-strike rule that stops blind guessing. - Verified Fixes with Regression Tests: Requires a minimal-diff fix, a regression test that fails without the fix and passes with it, a full test suite run, and a structured debug report saved to memory. - Use Case: A user reports an intermittent production error with a stack trace. The Skill traces the failure path, identifies a race condition on shared state, confirms it with a temporary log statement, applies a minimal fix, and ships a regression test plus a debug report. ## Quick Start Ask the agent to investigate and fix the error shown in this stack trace using systematic root cause analysis.

Frequently Asked Questions about gstack-openclaw-investigate

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

FAQPage Schema
How do I debug a bug systematically instead of guessing?

Follow a phased approach: collect symptoms and reproduce the bug, trace the code path and recent git changes, form one testable root cause hypothesis, confirm it with temporary logging, then apply a minimal fix with a regression test. Never fix before confirming the root cause.

How to find the root cause of an intermittent bug?

Intermittent bugs often indicate race conditions or timing-dependent state corruption. Gather evidence through instrumentation and logging at the suspected failure point, check concurrent access to shared state, and avoid proposing fixes until the failure is reproducible or strongly evidenced.

What should I do after multiple fix attempts fail?

Stop after three failed hypotheses. Repeated failures usually signal an architectural issue rather than a simple bug. Escalate for human review, add instrumentation to catch the bug next time, or continue only with a clearly stated new hypothesis.

Why write a regression test for every bug fix?

A regression test proves the fix works and prevents the bug from returning. It must fail without the fix and pass with it, confirming both that the test is meaningful and that the root cause was actually addressed.

When is a bug fix too large to ship safely?

A fix touching more than five files has a large blast radius for a bug fix and should be flagged before proceeding. Prefer the smallest change that eliminates the root cause, and resist refactoring adjacent code during the fix.