I have a `codex-review` skill with a shell script that uses the Codex CLI with a prompt. It tells Claude to use Codex as a review partner and to push back if it disagrees. They will go through 3 or 4 back-and-forth iterations some times before they find consensus. It's not perfect, but it does help because Claude will point out the things Codex found and give it credit.
replyMind sharing the skill/prompt?
replyNot the OP, but I use the same approach.
replyhttps://gist.github.com/drorm/7851e6ee84a263c8bad743b037fb7a...
I typically use github issues as the unit of work, so that's part of my instruction.
zen-mcp (now called pal-mcp I think) and then claude code can actually just pass things to gemini (or any other model)
reply