What problem does it solve?
This Skill helps you debug errors effectively by forcing a disciplined root-cause investigation before any fix, preventing whack-a-mole failures and repeated regressions.
Core Features & Use Cases
- Root-cause-first debugging: Collect symptoms, trace the failing code path, and identify the underlying cause before proposing changes.
- Pattern analysis and hypothesis testing: Match failures to common debugging patterns (race conditions, null propagation, state corruption, integration failures, config drift, stale caches) and then test hypotheses with targeted evidence.
- Controlled implementation and verification: Apply minimal diffs, add a regression test, run the full test suite, then produce a structured debug report and save it for future reference.
Use case example: When a production command “stopped working” with a stack trace and intermittent behavior, use this Skill to determine whether the issue is a race, a missing guard, a stale cache, or an integration/config mismatch—then verify the fix with a regression test.
Quick Start
Use the gstack-openclaw-investigate skill when you paste a stack trace and describe what stopped working, so it can guide you through root-cause analysis, hypothesis testing, and a verified fix.
