The Feed & Board

Stop scanning. Start with what's blocking.

PR Flow's primary interface replaces the endless scrolling of standard pull request pages. Every open PR is classified into smart views that put the next decision at the top of your list.

View Layouts

You can customize how PR Flow displays your queue depending on your workflow preferences:

Feed View: A unified, top-to-bottom list ranked strictly by priority. The item at the very top is the most urgent thing blocking your team. Feed View

Board View: A Kanban-style interface that separates PRs into columns: Needs, Waiting, and Done. Board View

Smart Lanes

Regardless of the view you choose, PR Flow classifies every PR into three distinct states based on its current metadata (approvals, requested reviewers, CI status, and threads).

1. Needs

This is your inbox. PRs land in the Needs lane if:

  • A teammate explicitly requested your review.
  • A PR you authored requires you to resolve requested changes or reply to an open thread.
  • A PR you authored has been fully approved and is ready for you to merge.

Reviews you owe surface above your own PRs.

2. Waiting

This is your outbox. PRs land in the Waiting lane if:

  • You authored the PR and are waiting on teammates to review it.
  • You started reviewing a teammate's PR, left comments or requested changes, and are waiting for them to address your feedback.
  • Someone else started reviewing that PR and left comments or requested changes.

3. Done

PRs move here temporarily once they are merged or closed, giving you a quick history of recent activity.

Visual Indicators

PR Flow uses subtle visual cues to help you scan your queue:

  • Age Borders: A 4px left border encodes the age of the PR (Fresh , Warm , Stale ).
  • State Chips: Small badges indicating approved, changes requested, merged, or the number of unresolved threads.
  • Risk Ramps: If AI features are enabled, a small dot (from safe to critical) indicates the complexity and risk of the diff.