evidence-first-bug-triage

Diagnoses reported failures in hooks, scripts, build steps, and scheduled jobs by checking what the system actually wrote to disk — directory contents, file sizes and timestamps, log tails, and one controlled manual reproduction — before any code is edited. Every run or edit that overwrites existing data, mutates state, spends money, or reaches beyond the machine requires explicit user confirmation, and all evidence — snapshots, log copies, captured run output — passes through a redaction step so credential values are never persisted or quoted. Use when a bug report is about to trigger code changes but nobody has observed the real error, or when expected output files arrive missing, empty, or suspiciously stale. Not for greenfield features, style-only refactors, or failures already explained by saved output.

Version

v1.0.0

Size

18 KB

Updated

2026-10-12

Your client verifies the signature before reading. This explicit manual read is available on every plan. Free automatically loads five chosen skills; paid plans automatically load relevant skills across the library.