bugfix

To fix a failing test with root-cause certainty, this Skill performs a debugger-style diagnosis to classify the bug before any code changes, then generates structured requirements for a verified one-shot correction.

The best way to apply a minimal diff repair is to enforce root-cause investigation first, convert the diagnosis into a requirements.md file, and delegate the actual code fix and verification to an execution pipeline.

You diagnose an error log by submitting the error description to trigger a root-cause-first analysis, which classifies the failure and outputs a structured requirements.md file to guide the verified correction.

When repeated bug fix attempts fail verification, a max-attempt circuit breaker triggers escalation and saves debug reports, preventing infinite loops and preserving diagnostic data for manual review.

Yes, you can fix bugs from a stack trace without regressions because the process enforces root-cause investigation first and executes a verified one-shot correction using a standard verification pipeline.

You do not need a full specification to start; you can provide an error description to generate a root-cause fix, with the option to switch to full specification escalation if the initial diagnosis requires it.