Remove slop

Clean code and writing while keeping their behavior, meaning, and the writer's voice.

Process

1. For code, use the caller's fixed point or compute the task branch's merge-base with its configured base branch. Inspect staged, unstaged, committed, and untracked task files in that scope. For writing, identify the supplied text or document. Keep unrelated material out.
2. Scan code against the code checks and prose against every writing rule below.
3. Rewrite with the smallest focused edit that fixes the slop. Match the surrounding code and the intended tone.
4. Self-audit. Ask what still makes the result look AI-generated or out of place, then fix any remaining tells.
5. Report the cleanup briefly, including any item you left unchanged because it would alter behavior or meaning.

Code

• Remove unnecessary comments and comments inconsistent with local style.
• Remove defensive checks or try/catch blocks that are abnormal for trusted code paths.
• Replace casts to any that only bypass type issues with a proper type or a simpler expression.
• Flatten deeply nested code with early returns when that matches local style.
• Remove other patterns inconsistent with the file and surrounding codebase.