What problem does it solve?
This Skill restores intended behavior by applying focused, evidence-based repairs for bugs and runtime failures when there is enough diagnostic information to act. It prevents speculative changes by requiring a clear failing area, reproducible test, concrete error path, or prior diagnosis before making code modifications.
Core Features & Use Cases
- Evidence-first repairs: Choose the minimal change that removes the root cause rather than masking symptoms.
- Call-stack upstream rule: Trace crashes to the producer of bad data and fix the producer or caller, not just the crash site.
- Verification and cleanup: Add or update durable tests, prove the failure is gone, exercise the repaired path, and remove temporary instrumentation once verified.
- Use Case: Fix a failing unit test caused by an off-by-one error, repair an API 500 by correcting a malformed database query, or resolve a rendering bug by tracing bad state to its origin.
Quick Start
Provide the failing test, error logs, and a short description of expected behavior and ask the fix skill to implement the minimal code change that removes the root cause and add verification.