gstack-openclaw-investigate
This skill enforces a disciplined debugging workflow: gather symptoms and code context, test hypotheses against known patterns, verify your theory before writing any fix, and document findings in a structured report. It prioritizes root cause discovery over quick patches, flagging when investigation stalls so you know when to escalate rather than guess.
gstack-openclaw-investigate helps you find the root cause of bugs and errors through systematic investigation before attempting any fix.
AI-generated summary based on this skill's SKILL.md
Install
garrytan/gstack/gstack-openclaw-investigate · repository language: TypeScript
git clone https://github.com/garrytan/gstack
cp -r gstack/openclaw/skills/gstack-openclaw-investigate ~/.claude/skills/gstack-openclaw-investigatenpx skillfed install garrytan/gstack/gstack-openclaw-investigateFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How do I investigate a stack trace systematically?
gstack-openclaw-investigate guides you through structured stack trace analysis by first isolating the symptom, then tracing the execution path backward from the error point to identify where the actual problem originates. Rather than jumping to fixes, the skill helps you test hypotheses against known failure patterns and verify your theory with evidence before writing any code change.
What's the best way to debug my code error?
gstack-openclaw-investigate enforces a disciplined workflow: gather symptoms and code context, test hypotheses against known patterns, verify your theory before attempting a fix, and document findings in a structured report. This approach prioritizes root cause discovery over quick patches, helping you avoid treating symptoms instead of solving the actual problem.
How can I find the root cause of a bug?
gstack-openclaw-investigate helps you trace code execution from symptom back to actual problem by systematically eliminating possibilities. The skill flags when investigation stalls so you know when to escalate rather than guess, and emphasizes verification through testing before committing to a solution.
Should I write tests after fixing a bug?
gstack-openclaw-investigate prioritizes writing regression tests to confirm your fix works and prevent recurrence. This is part of the structured debugging methodology—once you've verified the root cause and applied your fix, tests ensure the problem stays solved and document the failure mode for future reference.
How does gstack-openclaw-investigate help with unexpected behavior?
The skill provides a systematic debugging approach for unexpected behavior by helping you gather context, form testable hypotheses, and verify theories with evidence. It emphasizes disciplined investigation over guessing, flagging when you need to escalate and ensuring you document findings in a structured report.
SKILL.md
rendered from the published skill — quoted content, verbatim
Systematic Debugging
Iron Law
NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST.
Fixing symptoms creates whack-a-mole debugging. Every fix that doesn't address root cause makes the next bug harder to find. Find the root cause, then fix it.
Phase 1: Root Cause Investigation
Gather context before forming any hypothesis.
-
Collect symptoms: Read the error messages, stack traces, and reproduction steps. If the user hasn't provided enough context, ask ONE question at a time. Don't ask five questions at once.
-
Read the code: Trace the code path from the symptom back to potential causes. Search for all references, read the logic around the failure point.
-
Check recent changes:
bash git log --oneline -20 -- <affected-files>Was this working before? What changed? A regression means the root cause is in the diff. -
Reproduce: Can you trigger the bug deterministically? If not, gather more
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 1 file
openclaw/skills/gstack-openclaw-investigate/SKILL.md