A Gerrit code review dashboard that shows what needs attention next.
Gerrit is excellent at reviewing a change and famously indifferent to helping you decide which change to review. PR Flow connects to your instance over its API and ranks your open changes alongside the rest of your review workload.
A change is not a pull request, and tooling keeps pretending otherwise.
Gerrit's model predates the pull request and is genuinely different in shape. That difference is why the modern crop of code review tools quietly does not support it — and why Gerrit teams end up with the least help.
Changes and patchsets, not branches and force pushes
A Gerrit change is one logical commit that evolves through successive patchsets, tied together by a Change-Id trailer rather than by a branch name. There is no “branch with commits on it” to point a generic PR integration at, which is where most of them stop.
Review state lives in labels
Approval in Gerrit is a set of votes on review labels, not a single binary approved flag. It is a more precise model, and a harder one to summarize on a row — so most aggregators either ignore Gerrit or reduce it to something misleading.
Relation chains make order matter
Gerrit changes routinely stack, each one parented on the last. Reviewing the third before the first is wasted effort, and the dependency is not something a flat list of open changes tells you.
The dashboard is a query language
Gerrit's own dashboards are powerful and entirely manual: you get what you ask for in a search expression. That is great when you know exactly what to ask, and no help at all with the everyday question of what deserves your attention first.
Your Gerrit changes, in the same ranked queue as everything else.
No search expression required.
PR Flow classifies each open change by the state it is in — a review someone is waiting on you for, a change of yours with unresolved comments, work correctly parked with someone else — and orders the queue from there. The top of the list is the next thing that needs you, without you having written a query to find it.
- Smart views: Needs you · Your changes · Waiting on others · Recently done
- A 4px left border encodes age: fresh, warm, stale
- Unresolved comment counts on the row itself
- Star a change to pin it, or track one by URL
Dependent changes, linked.
Stacked work is normal in Gerrit, and reviewing it out of order wastes everyone's time. PR Flow links dependent changes so the queue tells you which one to start with, and an AI estimate of complexity, risk and review effort tells you roughly what you are signing up for before you open it.
- Stack awareness across dependent changes
- Effort estimates in minutes, so you can pick work that fits the gap
- Linked Jira, Linear and Trello tickets in context
- Press O to open a diff line in your editor — PR Flow knows Gerrit's ref scheme
Read the patchset, leave the comments, cast your verdict.
The review view renders a full unified diff with per-file “viewed” tracking. Add line comments, reply to threads, and submit approve, request changes or comment on Gerrit the same way you would on GitHub or GitLab — with everything staged and previewed before it leaves your machine.
- Nothing posts until you press submit
- PR Flow never merges or submits a change on your behalf
- Every write is recorded in a local audit log you own
Most Gerrit teams are not only a Gerrit team.
Gerrit tends to hold the platform, the firmware or the kernel-adjacent code, while newer services live on GitHub or GitLab. That split is exactly what makes review workload hard to see.
One queue for both halves
Changes and pull requests are ranked against each other, so “what should I review next?” has one answer instead of one per system.
Credentials stay local
The Gerrit HTTP password is encrypted in your OS keychain and only ever sent to your own instance. Nothing is stored on our side.
The same AI review
Diff summaries, complexity and risk estimates and inline findings work on Gerrit changes too, through your own AI provider.
See the whole picture on the pull request dashboard, or how the ordering works on the review queue page.
Gerrit specifics.
How does PR Flow connect to Gerrit?
Does it call my changes "pull requests"?
Can I review and vote from the app?
Does it work with an internal Gerrit that is not on the internet?
We use Gerrit for some repos and GitHub for others.
Keep reading
Give Gerrit the dashboard it never had.
Add your instance URL and an HTTP password, and see your open changes ranked by what needs you. Free for 14 days.