A Gerrit code review dashboard that shows what needs attention next.
See which changes Need you, which are Waiting on others, and which can wait. PR Flow keeps Gerrit's vocabulary and Code-Review voting in a desktop queue.
Gerrit changes need Gerrit-aware review state.
PR Flow keeps changes, patchsets, labels, and relation chains intact instead of flattening them into pull-request terminology.
Changes and patchsets, not branches and force pushes
Successive patchsets remain part of one change, so the queue and review view track the revision you are actually reading.
Review state lives in labels
PR Flow submits a Code-Review vote and reports the value Gerrit accepted. It does not imply that a +1 is the same as a required +2.
Relation chains make order matter
Relation chains expose the order of dependent changes so each layer can be reviewed in context.
The dashboard is a query language
Gerrit remains the source of truth. PR Flow adds an attention-ordered view without asking you to maintain another query.
Your Gerrit changes, in the same ranked queue as everything else.
No search expression required.
Reviews and replies you owe appear under Needs you; your submitted changes can wait under Waiting on others. Age and unresolved comments stay visible on the row.
- 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
Dependent changes, linked.
PR Flow maps relation chains from trunk to top. Every change also carries a review size — Quick, Medium or Deep dive — read from the change itself, and with Agent Pipelines configured, advisory complexity and risk as well.
- Stack awareness across dependent changes
- Review size read from the change, with or without AI
- Linked Jira, Linear and Trello tickets in context
Read the patchset, stage comments, send the vote.
Read the unified diff, stage line comments and replies, then send Gerrit's Code-Review vote. PR Flow's review submission is separate from Gerrit's Submit change action, and the finish sheet reports the vote Gerrit accepted.
- Nothing posts until you press submit
- Gerrit's Submit change action remains yours
- Every write is recorded in a local audit log you own
Keep Gerrit beside the rest of your review work.
If your week spans providers, Gerrit changes can share the queue with pull requests and merge requests without losing their own terminology.
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. PR Flow does not host it.
Optional AI review
With the relevant agents enabled, summaries, estimates, and inline findings run 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
Keep the next Gerrit action visible.
You still review, vote and submit changes. PR Flow keeps the queue and review workspace ready. Try it free for 14 days; a one-time licence keeps it after the trial.