#1
Ranked #1 of 2 in this category· 该品类排名 #1 / 共 2 个
GStack Investigate
No fixes until the root cause is real.
根因没坐实之前，不急着动手修。
CodexClaude CodeLocal terminalsLow risk · 低风险trusted · 官方/可信open source · 开源
Editor's verdict· 编辑结论
Strong alternative when the user wants a more code-oriented debugging loop.
当用户需要更偏代码调查的调试循环时，它是 Incident Investigate 的强替代。
Install in your tool装到你的工具里
Pick your tool and copy the command.选你常用的平台，复制命令即可。$codex /investigate
- 1
Clone or open the source repository garrytan/gstack.
装好后，按命令在 Claude Code / Cursor 中触发。
- 2
Locate investigate and import that folder using Codex's local skill workflow.
首次运行会读取仓库历史并写入本地 skill 配置。
- 3
Check the repo README for prerequisites before running the command below.
把工作目录指给它，按提示走完输出即可。
✓
Best for适合什么场景
- Structured debugging结构化调试
- Root-cause-first remediation根因优先修复
- Intermittent failures间歇性故障
✗
Not for不适合什么场景
- Quick copy edits快速文案改动
- Browser-only QA纯浏览器 QA
- Release announcements发布公告
vs alternativesvs 其他选择
Full compare table完整对比表 →#2Incident Investigate
No fixes until the cause is real.
diff · 差异Best for slowing down messy incidents just enough to avoid wrong fixes.
Canary Watch
Verify the live deploy before users tell you it is broken.
diff · 差异A deployment verification skill that watches a release after merge for console errors, broken pages, and visual drift.
Test Bench
Fill the obvious testing holes before CI embarrasses you.
diff · 差异A testing skill focused on missing coverage, flaky test isolation, and pragmatic high-signal test suggestions.
Audit notes审计备注
last reviewed 2026-04-22 · 复查Source源码open on GitHub · 公开✓
Author作者verified org · 已验证✓
Network网络访问read-only · 只读✓
Filesystem文件写入sandboxed · 沙箱✓
Dependencies依赖audited · 已审计✓
Telemetry遥测none · 无✓