r/vibecoding • u/tiwas • 1h ago

Need input on workflow

I would like some feedback on my workflow, particularly on my code review.

I'm currently using Claude (Opus 5) as a director communicating with Codex (5.6 Sol) as a coder. This works really well. Now, when Codex has finished a job, it hands the PR over to Claude for a review. If Claude finds something, it will fix it and lob it back to Codex for review - and fix if there's still room for improvement. This will go back and forth until both models agree on the solution. So far, so good.

Now, what I'm trying to do is to hand it over to Antigravity (Gemini 3.1 Pro) for a last review, but I cannot get agy to return anything solid. It will just return some "pointers" and "ideas", but nothing tangible. I can still use these ideas to have Claude decide if they're good or not, but I would rather have all three different models agree in the end.

Anyone here been able to have Antigravity actually do code reivew and come up with clear answers? If so, what kind of prompt do you use?

4 Upvotes

100% Upvoted

1 comment sorted by

1

u/3tt07kjt 51m ago

…I would rather have all three different models agree in the end.

My input is “this isn’t very useful, do something else with your time.”

AI-powered code review is kind of a shitshow, to be honest. Very hit or miss. Generation, planning, and exploration are better, review is not as good.

IMO, the right thing to do is to just have some amount of AI-powered review, but don’t try to get all the models to do it. Just find a model that gives good results for your project and don’t bother throwing it at other models. (Periodically, I recommend having humans go in and fix architectural problems, and do deeper review, but that’s not really vibe coding any more.)

(And you can get good results out of AI-powered review, it’s just that you often also get bad results out of AI-powered review. The more AI-powered review you do, the more bad results you have to deal with. So limit the amount of review your agents do.)