How I built an AI code review GitHub Action
ruby
dev.to
Code review quality depended on which senior was on duty. That was the bug. Not a missing linter, not a bad process doc - the review you got depended on who was around. So I built a GitHub Action to set a floor. This post is about the boring parts that actually took time: a Rack 3.2 gotcha that ate my webhook, a Sequel JSONB trap, and teaching an LLM to shut up. The shape of the thing The flow is simple on paper: PR opened/updated → GitHub sends a webhook → API pulls the diff