PRFlow

For engineering teams

Automate your
code review channel

Your team pastes pull request links into a Slack channel and asks for eyes. PRFlow does the posting, keeps every card current, and shows what still needs a reviewer.

Start free, up to 3 users

Works with GitHub, gitlab.com and self-hosted GitLab. No credit card required.

How many of the links in #code-review still need someone?

Every PR costs its author the same detour. Open the PR, copy the link, switch to Slack, find the channel, paste, type "can someone take a look?". Then the waiting starts. If nobody picks it up, the author asks again, DMs someone, or brings it up at standup. The reviewer who would have taken it never saw the message, because it scrolled away under the next five.

None of these steps is expensive on its own. They add up because they happen for every PR, they land at the exact moment the author wanted to start the next thing, and half the time the request is stale before anyone acts on it. CI failed, the branch got pushed again, the review already happened. The channel doesn't know any of that, so people open links that no longer need them and skip links that do.

Where the time goes

  • The context switch. Every PR pulls its author out of the editor and into Slack to post the link, then back again once someone answers.
  • The follow-up. A second ask, a DM, a standup mention. Chasing a review is work the author does instead of writing code, and it's the part engineers resent most.
  • The reviewer's scan. Scrolling the channel to work out which of the pasted links still needs someone, opening three to find one.
  • The missed ones. A PR nobody posted, or posted on a Friday afternoon, quietly rots until its author notices. That's the wait that shows up as slow cycle time, and nobody refused to review it.

The same channel, filled and kept current for you

Every PR posts itself

Open a PR and it appears in the channel you chose, as one card with the title, author and CI status. Nothing to copy, nothing to remember, no "please review" to type.

The card stays current

CI finishes, reviews land, the PR merges, and the same card updates in place. Review comments sync into that card's thread.

Read the channel at a glance

The rail colour encodes state, so a reviewer scanning the channel sees which PRs are still waiting on someone and skips the ones that aren't.

What's still open, on a schedule

A digest lists the open PRs per channel, so the ones that scrolled away come back into view without anyone asking.

Each channel watches the repositories you give it

Pick them one by one, match them by pattern, or send everything to one place. The frontend channel only ever sees frontend PRs.

Already have a bot posting PRs?

GitHub's and GitLab's own Slack apps post a message when a PR opens, and another message for every state change after that. Each message is frozen at the moment it was sent. A "ready for review" from Tuesday still says ready for review on Thursday, after the build broke and the PR merged anyway. The channel turns into a log, half the team mutes it, and reading a log to find what needs you is the same scan the pasted links needed.

PRFlow keeps one card per PR and edits it. The channel reads as a list of current state, which is what a review queue is supposed to be.

See how PRFlow compares to the native GitLab Slack app, or what it changes for GitHub pull requests.

Set it up once

01

Connect

Connect GitHub or GitLab, and Slack.

02

Pick the channel

Choose the channel your team already uses and which repositories post there.

03

Open a PR

It's in the channel before you've switched tabs.

Frequently asked questions

Can we keep our existing #code-review channel?

Yes. Pick it as the destination when you create the rule. Private channels work too, once PRFlow has been invited to them.

We use merge requests on GitLab. Same thing?

Yes. A GitLab merge request and a GitHub pull request get the same treatment: one card, kept current, in the channel you chose.

Does it work with self-hosted GitLab?

Yes. gitlab.com and self-hosted GitLab both work.

What does it cost?

Free for up to 3 users. After that, $4 per user a month, with a 14-day trial.

Let the channel fill itself

Connect GitHub or GitLab and Slack in minutes.

Start free, up to 3 users

Explore the other ways teams use PRFlow: for engineering managers · sharing merge requests · reviewing AI-generated MRs