I will set up codex to catch claude code bugs before they reach main


About this gig
I set up Codex to review Claude Code's commits in your repository before they merge. I write every setup from scratch for your repositories.
The setup includes:
1) The review gate in up to three repositories
2) Your tests run before every merge, and with review enforcement on, a commit Codex rejects doesn't merge
3) Review rules written for each repository's stack and conventions
4) A verdict file for every review, so each finding has a record your team can read
5) A first review on one of your real branches, with the findings explained in a recorded walkthrough
6) 14 days of fixes to the setup
I build my own projects this way, in Rails 8.1 and Next.js 16, and I've published how I make Codex review Claude Code commits.
You need Claude Code and Codex on accounts your team controls, and a test suite that runs from one command.
For companies registered in the UK or the US. Delivery days start when your requirements arrive.
Get to know Iliya Oblakov
MCP server developer and AI code review setup
- FromUnited Kingdom
- Member sinceSep 2019
Languages
English
FAQ
Do I need both Claude Code and Codex?
Yes. Claude Code writes the code and Codex reviews it, so your team needs both, on accounts you control.
Is this a template you copy into every repository?
No. I write the setup and the review rules for your repository, its stack and its conventions.
Will Codex stop every bad commit?
No. Your tests run before every merge, and with review enforcement on, a commit Codex rejects doesn't merge until it's fixed. Codex misses things too, so keep a human on the pull requests that matter most.
Will it work with my stack?
It works in a repository where Claude Code and Codex can run your tests from one command. Message me your stack before you order and I'll confirm it fits.
Do you need access to our code?
Yes, to the repositories in scope. I work on a branch, and you can remove my access the day I deliver.
What happens after delivery?
The setup lives in your repository and your team edits the rules as your conventions change. Fixes to the setup are included for 14 days.
