diagnosing-bugs
Diagnose hard bugs and performance regressions, and repair them when authorized. Use when the user asks to diagnose or debug, reports something broken/throwing/failing/slow, or explicitly asks to fix a suspected bug; default to diagnosis-only unless repair is requested.
- License 许可
- MIT
- 最近更新
- 2026-08-23
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- diagnosing-bugs
- description
- Diagnose hard bugs and performance regressions, and repair them when authorized. Use when the user asks to diagnose or debug, reports something broken/throwing/failing/slow, or explicitly asks to fix a suspected bug; default to diagnosis-only unless repair is requested.
02 资源文件 1
- 脚本scripts/hitl-loop.template.sh1.3 KB
03 SKILL.md 正文
Diagnosing Bugs
A discipline for hard bugs. Skip phases only when explicitly justified.
When exploring the codebase, read CONTEXT.md (if it exists) to get a clear mental model of the relevant modules, and check ADRs in the area you're touching.
Redact
This skill has you show commands, outputs and captured artifacts. Redact every secret first — write <REDACTED> in its place. Build loops against env vars, so the credential stays in the environment rather than in what you show. Captured artifacts carry auth headers: quote only the lines that carry the signal.
If the redacted output is not enough to diagnose the bug, say so and ask the user.
Request Mode
Classify the request before any mutation:
- Diagnosis only — run Phases 1–4 as needed, then stop with the failure-surface classification, supported causal finding, confidence and remaining unknowns, and repair options. Do not enter Phase 5.
- Diagnosis and repair — run the full loop only when the user explicitly asked to fix or change the system, or later authorizes one of the repair options.
When scope is ambiguous, default to diagnosis only. Permission for temporary instrumentation authorizes only that instrumentation, not the eventual repair.
Phase 1 — Build a feedback loop
This is the skill. Everything else is mechanical. If you have a tight pass/fail signal for the bug — one that goes red on this bug — you will find the cause; bisection, hypothesis-testing, and instrumentation all just consume it. 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.
Ways to construct one — try them in roughly this order
- Failing test at whatever seam reaches the bug — unit, integration, e2e.
- Curl / HTTP script against a running dev server.
- CLI invocation with a fixture input, diffing stdout against a known-good snapshot.
- Headless browser script (Playwright / Puppeteer) — drives the UI, asserts on DOM/console/network.
- Replay a captured trace. Save a real network request / payload / event log to disk; replay it through the code path in isolation.
- Throwaway harness. Spin up a minimal subset of the system (one service, mocked deps) that exercises the bug code path with a single function call.
- Property / fuzz loop. If the bug is "sometimes wrong output", run a budgeted random sample, record the observed failure rate, and retain failing seeds as fixtures.
- Bisection harness. If the bug appeared between two known states (commit, dataset, version), automate "boot at state X, check, repeat" so you can
git bisect runit. - Differential loop. Run the same input through old-version vs new-version (or two configs) and diff outputs.
- HITL bash script. Last resort. If a human must click, drive them with
scripts/hitl-loop.template.shso the loop is still structured. Captured output feeds back to you.
A tight feedback loop materially reduces uncertainty; it does not establish the cause or prove the repair.
Tighten the loop
Treat the loop as a product. Once you have a loop, tighten it:
- Can I make it faster? (Cache setup, skip unrelated init, narrow the test scope.)
- Can I make the signal sharper? (Assert on the specific symptom, not "didn't crash".)
- Can I make it more deterministic? (Pin time, seed RNG, isolate filesystem, freeze network.)
A loop is tight when it is specific and deterministic enough to compare probes, and cheap enough to rerun after every meaningful change within the task's diagnostic budget. Record its wall time and failure rate instead of applying a universal duration cutoff.
Non-deterministic bugs
The goal is not a clean repro but enough observed failures to compare hypotheses within the available time or cost budget. Measure the baseline rate, estimate expected failures per batch (attempts × rate), and choose a batch that should yield several observations. A low raw rate remains usable when attempts are cheap and agent-runnable; when expected observations are too sparse, parallelise, add stress, narrow timing windows, or inject sleeps until the loop becomes informative. Record the rate, batch size, run cost, and observed failures instead of applying a universal percentage cutoff.
When you genuinely cannot build a loop
Stop and say so explicitly. List what you tried. Ask the user for: (a) access to whatever environment reproduces it, (b) a redacted captured artifact (HAR file, log dump, core dump, screen recording with timestamps), or (c) permission to add temporary production instrumentation. Do not proceed to hypothesise without a loop.
Completion criterion — a tight loop that goes red
Phase 1 is done when the loop is tight and red-capable: you can name one command — a script path, a test invocation, a curl — that you have already run at least once (show the invocation and its output, redacted), and that is:
- [ ] Red-capable — it drives the actual bug code path and asserts the user's exact symptom, so it can go red on this bug and green once fixed. Not "runs without erroring" — it must be able to catch this specific bug.
- [ ] Deterministic — same verdict every run (flaky bugs: a pinned, high reproduction rate, per above).
- [ ] Affordable — cheap enough to rerun after every meaningful probe within the task's diagnostic budget; record its wall time and per-batch cost.
- [ ] Agent-runnable — you can run it unattended; a human in the loop only via
scripts/hitl-loop.template.sh.
If you catch yourself reading code to build a theory before this command exists, stop — jumping straight to a hypothesis is the exact failure this skill prevents. No red-capable command, no Phase 2.
Phase 2 — Reproduce + minimise
Run the loop. Watch it go red — the bug appears.
Confirm:
- [ ] The loop produces the failure mode the user described — not a different failure that happens to be nearby. Wrong bug = wrong fix.
- [ ] The failure is reproducible across multiple runs (or, for non-deterministic bugs, reproducible at a high enough rate to debug against).
- [ ] You have captured the exact symptom (error message, wrong output, slow timing) so later phases can verify the fix actually addresses it.
Classify the failure surface
Before calling the red signal "the bug", record one row per distinct failure:
| Field | Required content |
|---|---|
| Observed signal | Exact error, wrong output, timing, or rejection |
| Controlling contract | Assertion, schema, protocol, specification, or user expectation that makes it red |
| Expected | Required value or behavior |
| Actual | Observed value or behavior |
| Fault class | implementation defect, input defect, protocol prerequisite, substantive failure, or unknown |
| Causal impact | What this failure blocks or invalidates |
| Unaffected scope | Behavior, evidence, or verdicts this failure does not decide |
A validator rejection may be intended enforcement rather than a validator defect. Keep separate rows when one run exposes failures in different layers. Show the classification and a plain-language causal chain to the user before recommending repair; if the class remains unknown, do not imply that an implementation is defective.
Minimise
Once it's red, shrink the repro to the smallest scenario that still goes red. Cut inputs, callers, config, data, and steps one at a time, re-running the loop after each cut — keep only what's load-bearing for the failure.
Why bother: a minimal repro shrinks the hypothesis space in Phase 3 (fewer moving parts left to suspect) and becomes the clean regression test in Phase 5.
Done when every remaining element is load-bearing — removing any one of them makes the loop go green.
Do not proceed until you have reproduced and minimised.
Phase 3 — Hypothesise
Unless the direct-proof exception below applies, generate 3–5 ranked hypotheses before testing any of them. Single-hypothesis generation anchors on the first plausible idea.
Direct-proof exception. Skip the ranked set only when the red signal names the exact mismatch, the controlling assertion is current, and direct source bytes establish one complete causal chain. Record red signal → controlling assertion → expected → actual → mechanism plus one observation that would falsify the chain, and show it to the user. If any link is inferred, ambiguous, or contested, use the ranked-hypothesis path.
Each hypothesis must be falsifiable: state the prediction it makes.
Format: "If <X> is the cause, then <changing Y> will make the bug disappear / <changing Z> will make it worse."
If you cannot state the prediction, the hypothesis is a vibe — discard or sharpen it.
Show the ranked list to the user before testing. They often have domain knowledge that re-ranks instantly ("we just deployed a change to #3"), or know hypotheses they've already ruled out. Cheap checkpoint, big time saver. Don't block on it — proceed with your ranking if the user is AFK.
Phase 4 — Instrument
Each probe must map to a specific prediction from Phase 3. Change one variable at a time.
Tool preference:
- Debugger / REPL inspection if the env supports it. One breakpoint beats ten logs.
- Targeted logs at the boundaries that distinguish hypotheses.
- Never "log everything and grep".
Tag every debug log with a unique prefix, e.g. [DEBUG-a4f2]. Cleanup at the end becomes a single grep. Untagged logs survive; tagged logs die.
Perf branch. For performance regressions, logs are usually wrong. Instead: establish a baseline measurement (timing harness, performance.now(), profiler, query plan), then bisect. Measure first, fix second.
Phase 5 — Authorized fix + regression test
Enter this phase only on a diagnosis-and-repair request. A diagnosis-only run ends after the supported causal finding and repair options are delivered.
Artifact lifecycle gate
Before editing, read the repository or project convention that owns the target artifact and classify it as a mutable working surface or frozen, published, or custodied evidence. Mutate only a mutable owner. For frozen evidence, preserve the producing bytes, hashes, invalid attempts, and superseded artifacts, then use the owner's versioning or supersession route and rerun every downstream check it requires.
A stronger governing or companion workflow's custody, freeze, or supersession protocol takes precedence and is followed unchanged.
Write the regression test before the fix — but only if there is a correct seam for it.
A correct seam is one where the test exercises the real bug pattern as it occurs at the call site. If the only available seam is too shallow (single-caller test when the bug needs multiple callers, unit test that can't replicate the chain that triggered the bug), a regression test there gives false confidence.
If no correct seam exists, that itself is the finding. Note it. The codebase architecture is preventing the bug from being locked down. Flag this for the next phase.
If a correct seam exists:
- Turn the minimised repro into a failing test at that seam.
- Watch it fail.
- Apply the authorized fix at the earliest mutable owner, or create the governed superseding or versioned artifact when the lifecycle owner forbids in-place change.
- Watch it pass.
- Re-run the Phase 1 feedback loop against the original (un-minimised) scenario.
Phase 6 — Authorized-repair cleanup + post-mortem
Required before declaring an authorized repair done:
- [ ] Original repro no longer reproduces (re-run the Phase 1 loop)
- [ ] Regression test passes (or absence of seam is documented)
- [ ] All
[DEBUG-...]instrumentation removed (grepthe prefix) - [ ] Truly throwaway prototypes deleted (or moved to a clearly-marked debug location); captured traces, invalid attempts, frozen artifacts, and superseded evidence retained whenever the governing custody or provenance contract requires them
- [ ] The proven causal chain or hypothesis that turned out correct is stated in the commit / PR message — so the next debugger learns
Then ask: what would have prevented this bug? If the answer involves architectural change (no good test seam, tangled callers, hidden coupling) tell the user to run the improve-codebase-architecture skill with the specifics. Make the recommendation after the fix is in, not before — you have more information now than when you started.
04 同仓库更多 Skills
triage
Move issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.
triage
Move issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.
tdd
Test-driven development. Use when the user wants a red-green development loop or integration tests.
tdd
Test-driven development. Use when the user wants a red-green development loop or integration tests.
tdd
Test-driven development. Use when the user wants a red-green development loop or integration tests.
tdd
Test-driven development. Use when the user wants a red-green development loop or integration tests.