| ▲ | NitpickLawyer 4 hours ago |
| Just some anecdata++ here but I found 5.2 to be really good at code review. So I can have something crunched by cheaper models, reviewed async by codex and then re-prompt with the findings from the review. It finds good things, doesn't flag nits (if prompted not to) and the overall flow is worth it for me. Speed loss doesn't impact this flow that much. |
|
| ▲ | kilroy123 4 hours ago | parent | next [-] |
| Personally, I have Claude do the coding. Then 5.2-high do the reviewing. |
| |
| ▲ | _zoltan_ an hour ago | parent | next [-] | | I have Opus 4.5 do everything then review it with Gemini 3. | |
| ▲ | seunosewa 3 hours ago | parent | prev [-] | | Then I pass the review back to Claude Opus to implement it. | | |
| ▲ | kilroy123 27 minutes ago | parent | next [-] | | Sometimes, depends on how big of a task. I just find 5.2 so slow. | |
| ▲ | VladVladikoff 3 hours ago | parent | prev [-] | | Just curious is this a manual process or you guys have automated these steps? | | |
| ▲ | ricketycricket 2 hours ago | parent | next [-] | | 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. | | | |
| ▲ | _zoltan_ an hour ago | parent | prev [-] | | zen-mcp (now called pal-mcp I think) and then claude code can actually just pass things to gemini (or any other model) |
|
|
|
|
| ▲ | StephenHerlihyy 3 hours ago | parent | prev [-] |
| I don’t use OpenAI too much, but I follow a similar work flow. Use Opus for design/architecture work. Move it to Sonnet for implementation and build out. Then finally over to Gemini for review, QC and standards check. There is an absolute gain in using different models. Each has their own style and way of solving the problem just like a human team. It’s kind of awesome and crazy and a bit scary all at once. |
| |
| ▲ | readyforbrunch an hour ago | parent [-] | | How do you orchestrate this workflow? Do you define different skills that all use different models, or something else? |
|
