What problem does it solve? Bug-fix pull requests often balloon into unrelated refactors, formatting churn, or speculative generalizations, making them hard to review and risky to merge. This Skill enforces a disciplined workflow that corrects exactly one defect with regression evidence while leaving the rest of the codebase untouched. ## Core Features & Use Cases - Structured Bug Statement: Requires a precise When/Actual/Expected bug statement and a scope contract defining non-goals before any code changes. - Regression-Test-First Workflow: Guides writing a minimal failing test that reproduces the defect, then making the narrowest sufficient correction. - Specialized Bug Guidance: Covers error bugs, numerical bugs, alignment bugs, metadata bugs, compatibility bugs, and private-API breakage with tailored testing advice. - Use Case: A numeric selection function errors due to a misspelled accessor. Use this Skill to write a failing regression test, fix the one-line accessor call, verify nearby behavior is preserved, and produce a clean single-purpose diff. ## Quick Start Use the fix-one-bug skill to fix the numeric selection error in my package with a regression test and no unrelated changes.
