I am at a point where I would actually prefer to be the critic than the author.

If you told me my only job was to review PRs created by something like gpt6.1 on xhigh, I would have very little problem with this. As long as the upstream issues are kicked off by a human who is ultimately responsible for the outcome.

PR reviews can go very quickly if you get out of the ideology of owning every single line of code and begin focusing more attention on the data, schema and other structural elements of the solution.

I'm right there with you. And as I find things in reviews, I kick off sessions to setup guardrails so I hopefully never have to make the same comment twice.