trace
Evidence-driven tracing with competing hypotheses in parallel. Activate when user says: trace this, trace, why did this happen, root cause analysis, investigate why.
来源信息
- 仓库
- zereight/gitlab-mcp
- 最近来源活动
- 2026年4月12日 05:11
- 检测到的 SKILL.md 语言
- 英语
- 星标
- 2,091
- Forks
- 368
安装方式
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
检查来源文件
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
正在显示 SKILL.md
SKILL.md
来源说明 · 只读预览- name
- trace
- description
- Evidence-driven tracing with competing hypotheses in parallel. Activate when user says: trace this, trace, why did this happen, root cause analysis, investigate why.
- argument-hint
- <observation to trace>
# Trace
Evidence-driven causal tracing using competing hypotheses. Use for ambiguous, causal, evidence-heavy questions where the goal is to explain WHY something happened.
## Good Entry Cases
- Runtime bugs and regressions
- Performance / latency behavior
- Architecture / premortem / postmortem analysis
- Config / routing / orchestration behavior
- "Given this output, trace back the likely causes"
## Core Contract
Always preserve: Observation → Hypotheses → Evidence For → Evidence Against → Best Explanation → Critical Unknown → Discriminating Probe
## Workflow
1. Restate the observed result precisely
2. Generate 3 deliberately different hypotheses:
- Code-path / implementation cause
- Config / environment / orchestration cause
- Measurement / artifact / assumption mismatch
3. Assign @tracer to each hypothesis lane
4. Each lane: evidence for, evidence against, critical unknown, discriminating probe
5. Apply lenses: Systems, Premortem, Science
6. Rebuttal round between top two hypotheses
7. Rank, detect convergence, synthesize
## Output
```
### Observed Result
[What happened]
### Ranked Hypotheses
| Rank | Hypothesis | Confidence | Evidence Strength |
|------|------------|------------|-------------------|
### Most Likely Explanation
[Current best explanation]
### Critical Unknown
[Single missing fact]
### Recommended Discriminating Probe
[Single next probe]
```
在 GitHub 查看