What problem does it solve? Fixing bugs without a disciplined process leads to unverified patches, lost root-cause knowledge, and regressions that resurface later. This Skill takes a bug already registered in the Reversa bug registry and drives it through a controlled lifecycle: reproduction, root-cause diagnosis with epistemic states, risk assessment, approval-gated test and code changes, spec verdict, and policy-based closure. ## Core Features & Use Cases - Guided bug-fix lifecycle: Reproduces the bug with an evidence capsule, separates affected code from root cause (hypothesized/supported/confirmed), and optionally runs git bisect for regressions. - Two approval gates: Gate 1 covers reproduction and regression tests (demonstrated failing); Gate 2 covers the typed correction change set (demonstrated passing), with all diffs saved under fix/. - Spec verdict and closure policy: Compares the fix against the effective spec, generates versioned spec addenda when needed, and closes only when the project's closure policy (local-software, package, or production-service) is satisfied, locking the bug folder with DONE.md. - Use Case: A developer runs the skill on BUG-007, reviews the generated fix/plan.html, approves the failing regression test, approves the minimal patch, and closes the bug with full traceability. ## Quick Start Ask the agent to fix a registered bug by running /reversa-debugger-fix with the bug ID, for example: fix BUG-20260715-A7K3 using the reversa-debugger-fix skill.
