Find AI Code Slop

Review the diff between the working branch and its baseline, and propose removals for AI-generated slop. Do not modify files.

Resolve the baseline

Pick the first available reference, in order:

1. An explicit ref the user provides (e.g. "compare against develop", a commit SHA, or a tag).
2. The upstream tracking branch (git rev-parse --abbrev-ref --symbolic-full-name @{u}).
3. The repo's default branch (git symbolic-ref refs/remotes/origin/HEAD, falling back to main then master).
4. The merge-base of HEAD and the resolved ref above (git merge-base).

State the resolved baseline in the report so the user can confirm.

Comments: guilty until proven innocent

Treat every comment added in the diff as slop by default. A senior engineer writes almost none; the diff should read the same way. Do not look for reasons to flag a comment — flag it, then look for a reason to keep it. A comment survives only if it passes ALL of these: