> So now I have to review broken PRs at breakneck speed because everyone has gotten so productive that I've become a bottleneck. These PRs seem like they would

> So now I have to review broken PRs at breakneck speed because everyone has gotten so productive that I've become a bottleneck. These PRs seem like they would take mere minutes to identify as being slop, no? I guess if you're getting dozens of them, that can be a time-sink. In any case, it's good that you're a bottleneck; you're more than that, you're a sieve, preventing this crap from getting into the codebase. I, personally, would be up front: "This was written by AI, with zero tests and zero thought. It doesn't follow best practices, and will not be merged as is. I will be rejecting all PRs of this nature in the future." Then close the PR, and copy-and-paste as needed; after the third one, contact their manager.