Remove AI Code Slop

# Remove AI Code Slop

Remove AI Code Slop is a code review prompt for cleaning up diffs that feel machine-generated, over-defensive, or stylistically out of place. It is useful when a branch technically works, but the code still carries obvious AI artifacts that a strong human reviewer would want removed before merge.

## Best For

- Reviewing AI-assisted pull requests before merge
- Cleaning comments, defensive branches, and weak type escapes from a diff
- Tightening code so it matches existing file style and team conventions
- Running a final polish pass after a large AI-generated draft

## How To Use It

1. Give the assistant the current branch diff against `main`.
2. Ask it to edit only the suspicious or low-quality additions.
3. Keep the final report short so the output stays focused on code changes.
4. Pair it with tests or typechecks after the cleanup pass.

## What It Usually Removes

- Comments a human teammate would not write
- Defensive checks that do not fit trusted call paths
- `any` casts or similar escapes added only to silence errors
- Boilerplate try/catch wrappers that obscure the real logic
- Naming, structure, or formatting that clashes with surrounding code

## Prompt Template

Check the diff against main, and remove all AI generated slop introduced in this branch.

This includes:

- Extra comments that a human wouldn't add or is inconsistent with the rest of the file
- Extra defensive checks or try/catch blocks that are abnormal for that area of the codebase (especially if called by trusted or validated codepaths)
- Casts to any to get around type issues
- Any other style that is inconsistent with the file

Report at the end with only a 1-3 sentence summary of what you changed

## Example Follow-Up

```text
Be aggressive about removing anything that feels generic, over-explained, or unlike the rest of this file. Preserve behavior, keep the diff small, and do not add new abstractions unless they clearly simplify the code.
```

## Limitations

- This prompt is best at cleanup, not deep redesign.
- It can miss subtle architectural issues if you only provide a narrow diff.
- Always run project checks after the cleanup pass because small removals can still affect behavior.