Improving Claude's PR reviews with risk assessment and multi agent reviews#1641
Merged
Improving Claude's PR reviews with risk assessment and multi agent reviews#1641
Conversation
…ling if the PR needs a senior review. I will say that if it says low-risk and you want a senior review, nothing is stopping you from asking for one. This isa just a guide.
…0 each time to run, but will catch a lot of things.
dr-bizz
changed the title
Contributor
Bundle sizes [mpdx-react]Compared against 218dce0 No significant changes found |
Contributor
Author
|
canac
approved these changes
Feb 25, 2026
Contributor
canac
left a comment
canac
left a comment
There was a problem hiding this comment.
The agent swarm is interesting! I'm wondering if you have any data about it catching more than the original PR review command?
.claude/commands/agent-review.md
Outdated
| **Model Configuration**: | ||
|
|
||
| - Security: Sonnet (deep reasoning needed) | ||
| - Architecture: Sonnet (system thinking needed) |
Contributor
Author
There was a problem hiding this comment.
I think because that would make it super expensive
Contributor
Author
There was a problem hiding this comment.
I've switched them to opus. Good call
Contributor
Author
I do, It caught the cache issue on #1639 when |
dr-bizz
force-pushed
the
better-pr-reviews
branch
from
43cafab to
9168d8e
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
With PRs being written faster and with the PR review bottleneck, I wanted to implement a few new features to Claude's PR review command that will help us spread the PR review workload across more devs.
Adding Risk Assessment to the
/pr-reviewcommandDuring the review, it will inform you of a suggested risk assessment. It will score the PR from 0 - 10 on the scale of risk. Depending on what it edits, what time or day it is (Friday), knock on affects etc.
The suggested Risk assessment is a guide to help the dev know who to ask for a review.
Low or Medium risk means an entry-level or mid-level engineer can review it.
Critical or High risk means a senior dev should review it
Again, this is just a suggestion, and nothing is stopping you from asking a senior to review a low-risk PR.
Multi-agent review
/agent-reviewWith the release of teams on Claude, we're able to spin up multiple agents and give each one a skill (an area they are focused on, like Security, Architecture, Data, Testing or UX) which we run 2 rounds of debate to provide deeper analysis and ensure we review the PR with different lenses to ensure we catch errors or bugs that could be released into production.
We should run the ultimate review only once per PR, as it costs $0.80-$2.50 to run.
Checklist:
/pr-reviewcommand locally and fixed any relevant suggestions