Diagnosing Bugs

Discipline for hard bugs. Skip a phase only with reason. Use the domain glossary and ADRs; for third-party, API, or version drift, run /read-the-damn-docs before ranking hypotheses.

Redact

This skill exposes commands, output, and captured artifacts. Replace every secret with <REDACTED>. Keep credentials in environment variables and quote only signal-bearing lines; captured artifacts may contain authentication headers. If redaction removes necessary evidence, ask for a safer source.

Phase 1 -- Build a feedback loop

The feedback loop is the skill. Everything else consumes it. Build a tight, deterministic, agent-runnable pass/fail signal that goes red on the user's exact bug. Spend disproportionate effort here; code reading is for constructing the loop, not inventing an unsupported theory.