---
id: gh-investigate-first
name: "investigate-first"
url: https://skills.yangsir.net/skill/gh-investigate-first
author: juliusbrussee
domain: ai-system-observability-sre
tags: ["root-cause-analysis", "debugging", "troubleshooting", "investigation", "evidence-based"]
install_count: 101800
rating: 4.80 (120 reviews)
github: https://github.com/juliusbrussee/caveman/tree/main/skills/investigate-first
---

# investigate-first

> 此技能帮助开发者在遇到模糊错误、间歇性故障或性能回退时，先系统化收集证据、区分症状与根因、按证据排序假设，在找到确凿原因前不修改代码。通过追踪输入、状态与失败输出，显著缩短平均故障定位时间，避免盲目修改引入新问题。

**Stats**: 101,800 installs · 4.8/5 (120 reviews)

## Before / After 对比

### 故障定位时间大幅缩短

**Before**:

开发者在遇到偶发故障或性能回退时，往往凭直觉反复修改代码，平均需要 4 小时才能定位根因，过程中还可能引入新的回归。

**After**:

此技能引导开发者按证据链排查，先假设后验证，将平均故障定位时间压缩至 30 分钟，并显著降低误改风险。

| Metric | Before | After | Change |
|---|---|---|---|
| 平均故障定位时间 | 240分钟 | 30分钟 | -88% |

## Readme

# Investigate first

Gather evidence before changing product code.

- Separate observed symptom from inferred cause.
- Trace inputs, state transitions, ownership boundaries, and failure output.
- Rank hypotheses by evidence and cheap falsification value.
- Do not edit until one credible mechanism explains evidence.
- Stop exploration when evidence is sufficient to name cause or exact blocker.

Report cause and proof. Make no fix unless task authorizes implementation.


---
*Source: https://skills.yangsir.net/skill/gh-investigate-first*
*Markdown mirror: https://skills.yangsir.net/api/skill/gh-investigate-first/markdown*