If you are using LLMs to write code, using LLMs to review the MRs is wrong. The writing-time model already had the best context for spotting errors; an MR-time bot is a weaker pass with less information. And the part of review that genuinely needed a second mind — team priors, incident history, intent — is exactly what a second LLM session cannot supply. Close the loop upstream at prompt time and downstream at behavior, not on the diff.
Jaime Gago
Condensing systems from the vapor of data
Building
oasis
Active
Open evaluation standard for AI agents. Binary safety gates, independent verification.
oasis-spec.devjoe
Active
Go-based Kubernetes AI copilot. OASIS-tested end-to-end.
skillhub
Active
Claude Code plugin for authoring Claude Code plugins. MCP server, Apache 2.0.
github.com/jaimegago/skillhubWriting
- Essay If LLMs Write Your Code, LLM Code Review Is the Wrong Loop
- Launch Why I built OASIS
Earlier this year I started building Joe — a software infrastructure copilot. Then I needed a way to verify, before letting it touch anything real, that it would behave according to the rules I'd built into its code. Nothing I found fit. So I built OASIS.