As a last resort, do the code-review with a live pair programming session.

If they can't explain their own code then it is by default a bad pull request.

At the end of the day, everyone's time is being wasted on tokens and on the increasing cognitive complexity of AI generated code.

So if they say "idk Claude did it", what would you write in the PR review box?

	▲	Geezus_42 2 hours ago \| parent \| next [-]
		REJECTED: Engineer does not understand what they wrote.
	▲	CursedSilicon 2 hours ago \| parent \| prev [-]
		A teammate that can't write (or at least, can't explain) "their own code" Actively drags down the morale and productivity of their team (because everyone is getting flooded with AI slop PR's) AND costs far too much money relative to everyone else doing actual work? (token usage) By god they sound like management material