Review the change, not just the code.
Change Review starts from the ticket and gathers everything behind it. Hyrax then writes one short, plain-language review of the whole change.
Linear issue · every linked PR · review discussion · live flag state · never blocks a merge
No one sees the whole change.
Modern changes rarely live in one pull request. A single feature now spans a backend service, a web app, a mobile client and an infrastructure repo. It's written partly by AI coding agents, and it ships behind feature flags that decide who actually sees it.
Code review still happens one diff at a time. Reviewers check that each PR is well written, but no one checks that the PRs together deliver what was asked.
Change Review fills that gap. It starts from the ticket.
It gathers everything behind the ticket, then Hyrax writes one short, plain-language review of the whole change.
The ticket
The Linear issue, every requirement in it, and any acceptance criteria the team adds in plain words.
Every linked pull request
Across every repository, including the PR that hasn't merged yet.
The review discussion
The review discussion on each pull request.
The feature flags
The live state of the flags those PRs use, and where each is switched on today.
One short, plain-language review of the whole change.
- What's changingTwo or three sentences anyone on the team can read, not just the engineer who wrote it.
- Asked vs. builtEvery requirement in the ticket, checked against the code as met, partly met, not met or needs a person. Teams can add their own acceptance criteria in plain words.
- Before and afterWhat a user or admin will notice, written as a diff in plain English, with sketches of affected screens or system diagrams for backend changes.
- How it shipsWhich flags gate the change and where each is switched on today, including flags the code reads that were never created.
- Sources for every sentenceEach statement links to the PR, ticket or flag it came from, so nothing has to be taken on trust.
A feature is only done when every part of it is.
AI writes more of the code.
Line-by-line review doesn't scale when changes arrive faster than people can read them. Change Review raises the question to “is this the change we meant to make?”
Work spans repositories.
A feature is only done when every part of it is. Change Review sees all the parts at once, including the PR that hasn't merged yet.
Shipping is decoupled from merging.
With flags, “merged” doesn't mean “live”. Change Review shows who can see the change today, not just whether the code went in.
More people need to understand the change.
Product managers, QA, support and leadership get a readable account of what's shipping, without reading diffs.
It helps without getting in the way.
Change Review is advisory: it never blocks a merge. It sits alongside existing code review and gives the team a shared picture of the change before it reaches customers.
Book a demoChange Review is in early access.