Who it is for
For the engineer who reviews everybody else’s work.
You get a stated position on each change, the reasoning behind it, and a list of what was not checked, so the decision you own starts from something examined rather than from a diff and a deadline.
Where you are now.
- You are the person the queue routes to, because you are the one with the context.
- A large share of your week goes on reading other people’s changes, and it is the part of the job nobody accounts for.
- You approve things you have not fully traced, because tracing them properly would take the afternoon.
- The reviewer tools you have tried made the pull request louder rather than easier.
What changes.
- You start from a position, not a pile of parts
-
The assessment says whether the change looks safe, why, and how certain it is. You can disagree with it in one click, and your disagreement is recorded and used.
How the assessment is built - You can see what the change touches without tracing it yourself
-
The blast radius walks outwards from the change through the codebase map and marks the reached code your tests never exercise.
Blast radius - Somebody actually ran it
-
Where you have a staging environment, the affected flows have already been walked in a browser and anything that broke arrives as a recording.
Runtime evidence - You stop arguing about whose preference it is
-
Findings that come from your written conventions name the rule, so the conversation is about the rule rather than about taste.
Your standards
Add idempotency keys to the refund endpoint
7 files, +214 / -38, linked to billing-web #1902
Position
Safe to merge
It does what the ticket asked, it holds under the tests that touch it, and it behaves correctly in a browser. Nothing found rises to a reason to hold it.
How it got there
- Review Two findings raised, eleven suppressed as duplicates.
- Tests 214 affected tests run. All passed. Two written for gaps.
- Browser Refund and retry walked in staging. Nothing broke.
- Intent Matches PAY-1183.
Not checked
The webhook replay path, which your suite does not cover. Two tests written and attached. The payment provider sandbox was unreachable, so live retry behaviour is unverified.
Other people on the team
See it on your own pull requests.
We install on one repository, let Moonray AI assess the next changes your team opens, and go through what it found with you. If the position is not better than what you have now, you will know within a week.
Nothing to host. Reviews begin on the next pull request opened.