How are you managing code reviews in the AI era?
We’ve noticed that most of our tickets are getting stuck at the code review stage, mainly because PRs have become so large that they take much longer to review!
I’m curious to hear how you’re handling this in your team!
Commit
75242c9
I have one technical skill for code review, where subagents evaluate specific areas (architecture, security, etc.) and look for bugs. The second skill helps me break down and prioritize large PRs for my own review. So while the first skill is running, I go through the PR myself,…
I’m curious about the process behind your second skill. What does it highlight? Do you end up reviewing the code line by line?
Nope, it's no longer possible to go through these PRs line by line. I usually start by reading the tests, and then I move on to what the skill identifies as the core logic of that PR.
commit 75242c9