gstack-openclaw-investigate

Use when asked to debug, fix a bug, investigate an error, or do root cause analysis, and when users report errors, stack traces, unexpected behavior, or say something stopped working.

定位

Use when asked to debug, fix a bug, investigate an error, or do root cause analysis, and when users report errors, stack traces, unexpected behavior, or say something stopped working.

所属分组

openclaw/

核心流程/章节

• Iron Law
• Phase 1: Root Cause Investigation
• Phase 2: Pattern Analysis
• Phase 3: Hypothesis Testing
• Phase 4: Implementation
• Phase 5: Verification & Report
• Important Rules

原文要点

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. 1. Collect symptoms: Read the error messages, stack traces, an

适用场景

• 基于 description 推断：Use when asked to debug, fix a bug, investigate an error, or do root cause analysis, and when users report errors, stack traces, unexpected behavior,

参见

• GitHub: gstack
• 所属分组：openclaw/