> Pasting a big batch of new code and asking Claude "what have I forgotten? Where are the bugs?"

It's actually the main way I use CC/codex.

I find Codex sufficiently better for it that I’ve taught Claude how to shell out to it for code reviews

	▲	linsomniac 13 hours ago \| parent \| next [-]
		Ditto, I made a "/codex-review" skill in Claude Code that reviews the last git commit and writes an analysis of it for Claude Code to then work. I've had very good luck with it. One particularly striking example: I had CC do some work and then kicked off a "/codex-review" and while it was running went to test the changes. I found a deadlock but when I switched back to CC the Codex review had found the deadlock and Claude Code was already working on a fix.
	▲	cmrdporcupine 3 hours ago \| parent \| prev \| next [-]
		I think OpenAI has actually released an official version of exactly this: https://community.openai.com/t/introducing-codex-plugin-for-... https://github.com/openai/codex-plugin-cc I actually work the other way around. I have codex write "packets" to give to claude to write. I have Claude write the code. Then have Codex review it and find all the problems (there's usually lots of them). Only because this month I have the $100 Claude Code and the $20 Codex. I did not renew Anthropic though.
	▲	motbus3 7 hours ago \| parent \| prev [-]
		Yeah and it comes with the blood of children included

[dead]