gstack-openclaw-investigate

Diagnose bugs through root cause investigation, hypothesis testing, and verified fixes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Debugging often devolves into guessing and symptom-patching, which creates recurring bugs and whack-a-mole fixes. This Skill enforces a disciplined workflow that finds the actual root cause before any code change is made. ## Core Features & Use Cases - Root Cause Investigation: Collects symptoms, traces code paths, checks recent git history, and reproduces the bug before forming a hypothesis. - Pattern Analysis & Hypothesis Testing: Matches bugs against known patterns (race conditions, null propagation, state corruption, integration failures) and verifies hypotheses with temporary instrumentation, with a 3-strike stop rule. - Verified Fixes with Regression Tests: Requires a minimal-diff fix, a regression test that fails without the fix, 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, checks recent commits, confirms a race condition hypothesis with logging, applies a minimal fix, and ships a regression test plus a debug report. ## Quick Start Ask the assistant to investigate this error and find the root cause before fixing it, pasting the stack trace or describing the unexpected behavior.

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, verify it with temporary logging, then apply a minimal fix with a regression test. Never fix before confirming the cause.

How to find the root cause of an intermittent bug?

Intermittent bugs often indicate race conditions or timing-dependent state. Gather evidence through instrumentation and logging at the suspected failure point, check concurrent access to shared state, and avoid shipping any fix you cannot reproduce and verify.

What should I do when multiple fix attempts fail?

After 3 failed hypotheses, stop and question the architecture rather than guessing again. Escalate for human review, add instrumentation to catch the bug next time, or continue only with a clearly described new hypothesis.

Why does a bug keep recurring in the same files?

Recurring bugs in the same area are an architectural smell, not a coincidence. Check git history for prior fixes in those files and consider whether the underlying design, rather than individual code lines, is the root cause.

When should a bug fix include a regression test?

Every verified fix should include a regression test that fails without the fix and passes with it. This proves the test is meaningful, confirms the fix works, and prevents the same bug from reappearing in future changes.