{"enrichment":{"faq":[{"a":"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.","q":"How do I investigate a stack trace systematically?"},{"a":"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.","q":"What's the best way to debug my code error?"},{"a":"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.","q":"How can I find the root cause of a bug?"},{"a":"gstack-openclaw-investigate prioritizes writing regression tests to confirm your fix works and prevent recurrence. This is part of the structured debugging methodology\u2014once you've verified the root cause and applied your fix, tests ensure the problem stays solved and document the failure mode for future reference.","q":"Should I write tests after fixing a bug?"},{"a":"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.","q":"How does gstack-openclaw-investigate help with unexpected behavior?"}],"shadow_tags":["root-cause-analysis","systematic-debugging","error-investigation","bug-reproduction","hypothesis-testing","regression-detection","code-tracing","debugging-methodology","verification-workflow"],"summary_rewrite":"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."},"files":[{"bytes":5469,"path":"openclaw/skills/gstack-openclaw-investigate/SKILL.md","sha256":"ab4ef9f9482a1463cdd550333fc76be38ba5e786f901ce2888bee8452d94be20","url":"https://skillfed.io/files/garrytan/gstack/gstack-openclaw-investigate/50942c4a/SKILL.md"}],"id":"garrytan/gstack/gstack-openclaw-investigate","links":{"html":"https://skillfed.io/garrytan/gstack/gstack-openclaw-investigate","md":"https://skillfed.io/garrytan/gstack/gstack-openclaw-investigate.md","repo":"https://github.com/garrytan/gstack"},"meta":{"agents_supported":[],"first_seen":"2026-07-28","forks":18700,"language":"TypeScript","last_updated":"2026-07-15","license":"MIT","name":"gstack-openclaw-investigate","publisher":"garrytan","stars":124836},"relations":{"categories":["debugging","devops","quality-assurance"],"similar":[{"id":"FlorianBruniaux/claude-code-ultimate-guide/investigate"},{"id":"FerroxLabs/ijfw/ijfw-debug"},{"id":"duthaho/claudekit/investigate-root-cause"},{"id":"garrytan/gstack/investigate"},{"id":"softspark/ai-toolkit/debug"},{"id":"Mathews-Tom/armory/debug-investigator"},{"id":"catlog22/Claude-Code-Workflow/investigate"},{"id":"shipshitdev/skills/systematic-debugging"},{"id":"Pixel-Process-UG/superkit-agents/systematic-debugging"},{"id":"NousResearch/hermes-agent/systematic-debugging"}]},"slug":{"owner":"garrytan","repo":"gstack","skill":"gstack-openclaw-investigate"},"version":"50942c4a"}