How to deal with long vibe-coded PRs?

Question

Today I came across a PR for a (in theory) relatively simple service.It span across 9000 LOC, 63 new files, including a DSL parser and much more.How would you go about reviewing a PR like this?

zigcBenx · Accepted Answer

In my opinion no PR should have so much changes. It's impossible to review such things.
The only exception is some large migration or version upgrade that required lots of files to change.
As far it goes for Vibe coded gigantic PRs It's a straight reject from me.

aaronrobinson · Answer

Reject it

wengo314 · Answer

reject outright. ask to split it into reasonable chain of changesets.

JohnFen · Answer

I'd just reject it for being ridiculous. It didn't pass the first step of the review process: the sniff test.