No fixes until the root cause is real.
根因没坐实之前，不急着动手修。
Best when the bug lives inside the code itself, not in operational state. Same "no fixes until the root cause is real" discipline as incident-investigate, but biased toward static code investigation: reads suspect modules, builds a hypothesis tree, asks for a failing test or repro before proposing a change. Strongest on flaky tests and intermittent failures where shallow patches make things worse. For ops-side incidents (logs, traffic, infra), incident-investigate fits better.
bug 是在代码里而不是在运行态时，它最合适。和 incident-investigate 一样有「根因没明确前不修复」的纪律，但更偏静态代码调查：读可疑模块、建假设树、要求先有失败测试或复现，才允许改代码。在 flaky test 和间歇性故障这种「浅修反而更糟」的场景里最强。运维侧事故（日志、流量、基础设施）用 incident-investigate 更合适。
Use npx skills add to install this skill into the selected agent. Phase 0 commands are generated from source rules, not verified.
npx skills add https://github.com/garrytan/gstack/tree/main/investigate -g -a codex -yDrop `-g` to install project-locally
No fixes until the cause is real.
Verify the live deploy before users tell you it is broken.
Fill the obvious testing holes before CI embarrasses you.
| this skill · 当前GStack Investigate | Incident Investigate | Canary Watch | Test Bench | |
|---|---|---|---|---|
| Rating · 评分 | 4.8 | 4.8 | 4.6 | 4.4 |
| Stars · 星标 | 123k | 10k | 8.2k | 6.1k |
| Risk · 风险 | Low risk · 低风险 | Low risk · 低风险 | Medium risk · 中风险 | Low risk · 低风险 |
| Best for · 最适合 | Structured debugging | Root-cause analysis | Verify the live deploy before users tell you it is broken. | Fill the obvious testing holes before CI embarrasses you. |
| Not for · 不适合 | Quick copy edits | Quick cosmetic fixes | Workflows that require stronger human review than this catalog entry documents. | Workflows that require stronger human review than this catalog entry documents. |