Code review is one of those tasks that looks passive but drains you fast. You're context-switching between your own work and someone else's mental model, trying to be thorough without being slow. I started using AI as a first-pass review layer a few months ago, and it's changed how I approach the whole process. Here's exactly how I do it — copy-paste ready. The Problem With "Just Reading" a PR When you open a PR cold, you're doing three things at once: Building a mental model of what changed and why Spotting logic errors, edge cases, and style issues Thinking about downstream effects (tests, dependencies, API contracts) Most of us do all three simultaneously, which means we do all three worse. AI doesn't replace your judgment — but it handles the scaffolding so you can focus on the things only you can catch. Step 1: Dump the Diff Into Context Start by copying the raw diff from the PR. Most platforms (GitHub, GitLab) have a "view file" or copy-paste friendly diff view.…