Clean Code

Improve only the code changed in the current task. Preserve behavior, public APIs, and repository conventions. Favor small, evident improvements over speculative abstractions or broad rewrites.

Establish scope

1. Read repository instructions and determine which changes belong to the current task from conversation context and version-control diffs.
2. Inspect staged, unstaged, and relevant untracked files. Distinguish task changes from pre-existing user changes; never claim or rewrite unrelated work.
3. Focus on added or modified lines. Touch nearby code only when needed to understand the change or make a safe, coherent cleanup.
4. Exclude generated files, vendored code, lockfiles, snapshots, minified files, and third-party sources unless explicitly included.
5. If the user asks only for a review, report actionable findings with file and line references without editing. If they ask to clean up, finish, polish, or implement, apply safe fixes.

If the task boundary remains ambiguous and editing could overwrite unrelated work, stop and ask for clarification. Otherwise, state the chosen scope and proceed.

Review in context

Read enough surrounding code, call sites, tests, types, configuration, and documentation to understand behavior and local conventions. Use history only when the current code and task context do not explain an important choice.

Prioritize changes that make the edited code easier to understand, modify, and verify: