What problem does it solve? Applying bug fixes without a clear diagnosis or verification often introduces new regressions, runaway fix loops, and broken tests. This Skill enforces a disciplined locate-change-verify workflow so every code change is grounded in a root-cause diagnosis and validated before being reported. ## Core Features & Use Cases - Diagnosis-Gated Fixing: Requires a debug report or clear error before touching code, and classifies errors into a recovery policy matrix (auto-fix, retry, prompt user, abort, or re-diagnose). - Quality Decay Self-Regulation: Tracks a WTF-likelihood score across repeated fixes and stops when continued changes risk making things worse, with a hard cap of 30 fixes per session. - Defense-in-Depth Hardening: Adds validation at entry point, business logic, environment, and instrumentation layers so fixed bugs become structurally impossible. - Use Case: After a debug session identifies a null-pointer root cause in an auth module, invoke this Skill to apply the minimal fix, run the failing test then the full suite, verify types and lint, and emit a structured Fix Report with a DONE or DONE_WITH_CONCERNS status. ## Quick Start Ask the agent to apply the fix from the latest debug report and verify it with the project's test suite and type checker.