Review queue

Your review queue, ordered by what actually needs you.

“What should I review next?” is a real question with a real answer. It just is not one a chronological notification feed or a repository's pull request list can give you.

Download free The full dashboard

PR Flow — Needs you

Three different things

A feed, a list, and a queue are not the same object.

Most tools give you the first two and let you assemble the third in your head, several times a day.

A notification feed

Ordered by when something happened. Someone pushed, someone commented, a check went red. It is a log of events, and an event is not a task — the same pull request generates a dozen of them and none says whether it is now waiting on you. Marking one as read clears the notice, not the work.

A repository PR list

Ordered by where the code lives. Complete and accurate for exactly one repository, which is the wrong unit if your week spans six of them or two providers. It also has no opinion: an urgent review and a draft nobody wants sit in the same flat list.

An attention-ordered queue

Ordered by who is blocked. Every open pull request is resolved to its current state, then ranked so the top row is the next thing that needs a decision from you. This is the object you actually wanted, and it is what PR Flow builds.

How the ordering works

Classify by state, then rank by who is waiting.

Reviews you owe come first

Other people's blocked work outranks your own.

A pull request where you are a requested reviewer has someone waiting on the other end. One you authored and submitted is not blocked on you at all. So reviews you owe surface above your own pull requests — a small rule that changes what the top of the list means.

Needs you — a review requested, or changes requested on your PR
Your PRs — what you opened, and what is holding each one up
Waiting on others — correctly out of your hands, and quiet
Recently done — merged and closed, for the weekly recap

review requested changes requested 3 unresolved

Needs you · feed

Age is a first-class signal

Stale pull requests get harder to ignore, not easier.

In a chronological feed, a review from last Thursday sinks as newer items arrive above it — the item most likely to be blocking someone becomes the least visible. PR Flow encodes age as a coloured border on the row itself, on the same green-to-amber-to-red ramp used for risk, so an ageing review gets louder rather than quieter.

Fresh, warm and stale rendered on every row
Digest notifications call out what has gone stale
Nudge the right teammate when your own PR is stuck — previewed before it sends

PR Flow · menu bar

What the ranking reads

Signals that say who currently holds the ball.

Unresolved threads

The most honest indicator of who owes the next move. Counted on the row, and summarizable into what was asked, what was clarified and what is still open.

Review state

Review requested, changes requested, approved, draft, merged — the actual state of the pull request rather than the last thing that happened to it.

Age and staleness

How long the current state has held. The signal that makes blocked work visible instead of letting it sink.

Your own override

Star anything to pin it to the top, and track any pull request by URL even if it is outside your usual repositories.

Effort, when you enable AI

Complexity, risk and a rough time in minutes, so you can pick a review that fits the half hour you actually have. Advisory, and captioned with the model that produced it.

Stack position

Dependent pull requests are linked, so the queue can put the one that unblocks the others first.

Burn it down

A queue is only useful if you can work it.

Ordering the list is half the job. The other half is being able to act on the top item without opening a browser, losing your place, and coming back to re-read the list.

Full unified diff with per-file “viewed” tracking
Approve, request changes or comment — on GitHub, GitLab & Gerrit
“Submit & next” moves you straight to the following item
Keyboard-driven throughout; nothing posts until you press submit

The queue spans GitHub, GitLab, Gerrit and Azure DevOps at once.

Review · acme/web-app #101

Questions

How the queue behaves.

Can I override the ordering?

Yes. Star a pull request and it floats to the top of the queue regardless of what the ranking thinks — for the review you promised to do this morning, or the one your lead just asked about. You can also track any pull request by URL, including ones outside your normal queue.

How does it know something has gone stale?

Age is rendered directly on the row as a 4px left border on a green-to-amber-to-red ramp: fresh, warm, stale. It is a property of the row rather than a separate report, so an ageing review gets visibly harder to ignore the longer it sits there — which is the opposite of what a chronological feed does to it.

Will it notify me constantly?

No. The default is a quiet unread count in the menu bar. Beyond that you get digest notifications at times you pick — what needs you, what has gone stale, roughly how many minutes of review are queued — rather than a ping per event. Both are configurable in Settings.

What does the effort estimate actually estimate?

If you enable AI features, PR Flow asks your configured provider for a complexity band (easy through extreme), a risk band (safe through critical), and a rough review time in minutes. They are advisory numbers to help you pick work that fits the time you have, and every result is captioned with the provider and model that produced it. Estimates are marked outdated when new commits land.

Does the queue work without AI turned on?

Yes. Classification and ranking are built on review state, unresolved threads and age — all read straight from your providers. AI adds summaries, complexity and risk estimates and inline findings on top, and if you never enable it, none of your pull request content is sent to any AI provider.

Find out what your queue actually looks like.

Ranked against your own open pull requests, not a demo dataset. Free for 14 days, no account required.

Download free See pricing