What problem does it solve? Defects found mid-work often get lost, vaguely described, or closed without proof. This Skill maintains a single BUGS.json register where every entry carries its reproduction, observed versus expected behavior, root-cause mechanism, and the verification that fails without the fix. ## Core Features & Use Cases - Validated writes via the bugs binary: bugs add and bugs update enforce required fields and fixed vocabularies for status, severity, and priority, refusing malformed entries. - Evidence-backed closure: Marking an entry fixed requires both a fix reference and a verification naming the mutation that fails without it; dismissals require reasoning. - Register maintenance tooling: Commands for tree/report/list views, schema migration between versions, merge-conflict resolution, and duplicate-id deduplication. - Use Case: During a code review you find a heading-rename bug you cannot fix now. Run bugs add with the reproduction command and observed output, then later close it with the commit hash and the test that proves the fix. ## Quick Start Ask the agent to record the defect you just found as a new entry in BUGS.json using the bugs command with its reproduction steps and observed output.