boy-scout-rule

Apply the boy-scout rule to make small, safe, scoped improvements on every touched file. Enforce commit discipline with separate cleanup commits and documentation notes to prevent creeping debt during regular feature work and bug fixes.

Maintain clean code by enforcing commit discipline with separate cleanup commits and documentation notes. Observe touched files during reviews, make tiny safe edits like adding missing type annotations, and commit them separately from new features.

Incremental code maintenance works by requiring change-local edits scoped to touched files. You make tiny safe improvements like removing dead imports or renaming variables for clarity, then commit them separately to ensure every hotfix leaves code better.

Yes, incremental improvement applies to pair programming and code reviews. It encourages consistent cleanup across edits, steadily improving readability and maintainability through small, safe, scoped improvements on touched files.

Cleanup commits should be separated to enforce commit discipline during code maintenance. This separation ensures small, safe improvements like renaming variables or adding type annotations are clearly documented, preventing creeping debt and maintaining clean code after changes.