developer

To make a small bug fix safely, you need disciplined verification and limited scope. This involves carefully reading the affected code, making focused edits, running the narrowest relevant tests, and reviewing the diff before declaring the task complete.

Bounded refactoring that avoids public contract changes requires applying minimal-scope coding techniques. This ensures reversible cleanup work stays fast and reviewable by restricting changes to implementation details within one or a few files.

You need to run narrow tests during implementation work when verifying small, correct code changes. Verification discipline requires running only the narrowest relevant tests or lint checks after focused editing to confirm the update works.

Minimal-scope coding is best suited for bounded code changes in one or a few files. While it handles implementation updates, its core design focuses on limited scope to ensure changes remain fast, safe, and highly reviewable.

Code refactors cause unintended side effects when they lack disciplined verification and exceed limited scope. To prevent this, you must carefully read affected code before editing, avoid public contract changes, and review the diff upon completion.