diagnose

Installation
SKILL.md

Diagnose

Pattern-match is not diagnosis. A familiar symptom gives you a hypothesis. The diagnosis is an artifact of proof that links symptom → mechanism → cause. When the chain will not close, report the links you could support, the open hypotheses, and the smallest missing evidence.

Act or assess: an assessment ends with the diagnosis and its evidence. Only a requested fix goes on to Fix and verify.

Start from the evidence

Read the error, logs, traces, values, and failing results, then the code path they point to. Confirm they come from the affected version and conditions. Existing evidence can prove the cause without a fresh reproduction: "The trace is the artifact of proof: the retry leaves the connection open, which exhausts the pool."

Close the open questions

Use the moves that resolve the uncertainty you still have:

  1. Reproduce with the command, input, and environment that confirm or reject the open hypothesis. Record the exact command and output.
  2. Bound attempts. Set an attempt or time limit before repeating a probe, or reuse the caller's. A repeated failure does not reset it.
  3. Minimize the input or setup when that separates candidate causes or yields a regression case.
  4. Cheapest discriminating probe. When several causes fit, pick the probe whose outcomes tell them apart.
  5. Instrument only where evidence is missing. Preserve the failure state, and account for any effect the probe has on timing.
Installs
62
GitHub Stars
2
First Seen
Jul 30, 2026