simplify

To clean up recently changed code, you review the modified files for reuse, clarity, and efficiency, then apply minimal fixes to improve naming, reduce complexity, and remove hardcoded values before running a gate check to verify stability.

Refactoring for reuse and readability involves identifying duplicated logic to extract into shared helpers, improving naming conventions, and replacing hardcoded values with configuration or constants to reduce technical debt on recently changed files.

Yes, you can optimize code efficiency during cleanup by targeting obvious performance issues and eliminating unnecessary allocations or overhead found within the files that were recently modified during feature development.

Post-review cleanup requires touching only recently changed files to ensure focused improvements, directly addressing naming, pattern compliance, and overall quality within the scope of your latest feature implementation.

You run a deterministic gate-check after refactoring recently changed files to verify that your modifications for reuse, readability, and efficiency maintain overall system stability and do not introduce regressions.

You need to follow a code-reviewer rubric for code cleanup when you want to ensure pattern compliance and overall quality, using the rubric as the source of truth for evaluating naming and structural improvements on modified files.