AI Code Slop Reviewer Prompt

AI code review prompt to identify and remove AI-generated slop — excessive comments, unnecessary defensive code, type workarounds, and over-engineering

You will be reviewing a code diff against main to identify and remove "AI code slop" - unnecessary or stylistically inconsistent code that was likely added by AI code generation tools. Your goal is to produce a cleaned version of the diff with all such slop removed.

"AI code slop" refers to code patterns that are characteristic of AI-generated code but inconsistent with human coding practices or the existing codebase style. Specifically, you should identify and remove:

1. **Excessive or unnatural comments**: Comments that over-explain obvious code, are overly verbose, or are inconsistent with the commenting style in the rest of the file. Human developers typically comment sparingly and only for complex logic.

2. **Unnecessary defensive programming**: Extra try/catch blocks, null checks, or validation that is abnormal for that area of the codebase, especially in code paths where inputs are already trusted or validated upstream.

3. **Type system workarounds**: Casts to `any` or other type assertions used to bypass TypeScript/type checking issues rather than properly fixing the types.

4. **Stylistic inconsistencies**: Any code patterns, naming conventions, formatting choices, or structural approaches that differ from the established patterns in the file or codebase.

5. **Over-engineering**: Unnecessarily complex solutions where simpler code would suffice and match the codebase style.

To complete this task:

First, use a scratchpad to analyze the diff:

- Review each changed section in the diff
- Compare additions against the context of existing code
- Identify specific instances of AI slop with line references
- Note the patterns that appear to be AI-generated versus human-written

Then, provide the cleaned diff with all AI slop removed. The cleaned diff should:

- Maintain all legitimate functional changes
- Remove only the slop elements identified above
- Preserve the diff format (showing what was added/removed)
- Keep code that is functionally necessary and stylistically consistent

Your final output should be the complete cleaned diff. Present this inside <cleaned_diff> tags. If no slop was found, return the original diff unchanged and note that no changes were needed.