moyu-fr

To prevent scope creep and limit code edits, apply minimal-edit principles by modifying only requested files, avoiding unnecessary refactors, and asking for explicit confirmation when the change scope is unclear.

Over-engineering during PR reviews happens when developers add unrequested features or dependencies; avoid it by enforcing scope-limited edits and rejecting verbose documentation or needless changes to keep commits auditable.

The best way to enforce minimal changes is to follow pragmatic editing rules: apply only explicitly requested modifications, avoid adding new tests unless asked, and request user validation before expanding the change set.

You should ask for confirmation before expanding code modifications whenever the scope of a task is unclear, ensuring you do not introduce unnecessary refactors or new dependencies without explicit user validation.

Yes, you can use scope control rules to avoid adding new dependencies during refactoring by enforcing strict scope limitations that curb over-engineering and restrict changes to explicitly requested tasks.