#2
Ranked #2 of 2 in this category· 该品类排名 #2 / 共 2 个
Incident Investigate
No fixes until the cause is real.
原因还没坐实之前，不急着修。
CodexClaude Codelocal terminalsLow risk · 低风险open source · 开源
Editor's verdict· 编辑结论
Best for slowing down messy incidents just enough to avoid wrong fixes.
适合把混乱事故慢下来一点，避免错误修复。
Install in your tool装到你的工具里
Pick your tool and copy the command.选你常用的平台，复制命令即可。$codex /investigate
- 1
Clone or open the source repository evan-hsu/incident-investigate.
装好后，按命令在 Claude Code / Cursor 中触发。
- 2
Locate repository root 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适合什么场景
- Root-cause analysis根因分析
- Flaky bug investigation不稳定 bug 调查
- Post-incident summaries事故后总结
✗
Not for不适合什么场景
- Quick cosmetic fixes快速样式修补
- Tasks with no evidence available没有证据的任务
- Final production changes without review未获用户确认的最终生产变更
vs alternativesvs 其他选择
Full compare table完整对比表 →QA Loop
Open the product, try the flow, fix what breaks, repeat.
diff · 差异Best browser QA pick for teams that need visible evidence instead of a quick local glance.
#1GStack Investigate
No fixes until the root cause is real.
diff · 差异A structured debugging skill from gstack that forces evidence gathering, hypothesis testing, and root-cause-first remediation.
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.
Audit notes审计备注
last reviewed 2026-04-22 · 复查Source源码open on GitHub · 公开✓
Author作者community · 社区!
Network网络访问read-only · 只读✓
Filesystem文件写入sandboxed · 沙箱✓
Dependencies依赖audited · 已审计✓
Telemetry遥测none · 无✓