4 ms·
Then I pass the review back to Claude Opus to implement it.
by seunosewa 9mo ago
Then I pass the review back to Claude Opus to implement it.
- VladVladikoff 9mo agoJust curious is this a manual process or you guys have automated these steps?
- ricketycricket 9mo agoI 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.
- bryanlarsen 9mo agoMind sharing the skill/prompt?
- dror 9mo agoNot the OP, but I use the same approach. https://gist.github.com/drorm/7851e6ee84a263c8bad743b037fb7abc https://gist.github.com/drorm/7851e6ee84a263c8bad743b037fb7a... I typically use github issues as the unit of work, so that's part of my instruction.
- _zoltan_ 9mo agozen-mcp (now called pal-mcp I think) and then claude code can actually just pass things to gemini (or any other model)
- kilroy123 9mo agoSometimes, depends on how big of a task. I just find 5.2 so slow.