Diagnosing Bugs A discipline for hard bugs. Skip phases only when explicitly justified. When exploring the codebase, read (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 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,…