diagnose

Installation
SKILL.md

诊断 (Diagnose)

疑难 bug 的纪律。仅在有明确理由时才跳过阶段。

A discipline for hard bugs. Skip phases only when explicitly justified.

探索代码库时,使用项目的领域词汇表来建立相关模块的清晰心智模型,并检查你正在修改区域的 ADR。

When exploring the codebase, use the project's domain glossary to get a clear mental model of the relevant modules, and check ADRs in the area you're touching.

阶段 1 — 建立反馈循环 (Phase 1 — Build a feedback loop)

这才是核心技能。 其余都是机械操作。如果你拥有一个快速、确定性、agent 可运行的 pass/fail 信号来检测这个 bug,你就能找到原因——二分法、假设检验和埋点都只是在消费那个信号。如果没有,盯着代码看再多也无济于事。

This is the skill. Everything else is mechanical. If you have a fast, deterministic, agent-runnable pass/fail signal for the bug, you will find the cause — bisection, hypothesis-testing, and instrumentation all just consume that signal. If you don't have one, no amount of staring at code will save you.

在这里花不成比例的精力。要激进。要创造。拒绝放弃。

Spend disproportionate effort here. Be aggressive. Be creative. Refuse to give up.

Related skills

More from ninehills/mattpocock-skills

Installs
1
GitHub Stars
31
First Seen
Today