One review board for every open Bitbucket pull request
See every open pull request across all your Bitbucket repositories in one place, grouped by reviewer, with the ones that have been sitting too long flagged in red.
Bitbucket
Slack BotEngineeringResearch & MonitoringNotifications & AlertsBuild me an app my engineering team opens every morning to work our code review queue across all of our Bitbucket repositories. Bitbucket has no cross-repo pull request dashboard, so today we click into each repository one at a time to find what is waiting on us. This app should be the one screen that replaces that.
The main view is a board of every open pull request in the workspace. Load it by calling List Repositories in Workspace to get the repositories the connected user can see, then List Pull Requests for each one, keeping only pull requests in the OPEN state. Let the person configure which workspace to read and optionally narrow to a subset of repositories, since large workspaces have archived repos nobody reviews.
Organize the board into three columns: waiting on review, changes requested, and approved but not merged. Derive the column from the reviewer participation on each pull request, which comes back on the pull request record and in List Pull Request Activity: if a reviewer has recorded changes requested it goes in the middle column, if it has the approvals it needs but is still open it goes in the third column, otherwise it is waiting on review. Within each column, group the cards by reviewer so each person can see their own stack.
Each card shows the pull request title, the repository it belongs to, the author, the assigned reviewers, and its age in business days. Add the comment count from List Pull Request Comments and the number of still-unchecked items from List Pull Request Tasks, since a pile of unresolved comments or open checklist items is the real signal that a review is stuck. Business day math should skip weekends. Flag any pull request that has been sitting more than two business days in red, where sitting means business days since the last reviewer activity on it, falling back to when it was opened if no reviewer has touched it yet.
Every person should be able to toggle the board down to just the pull requests where they are the reviewer, so the same app doubles as a personal queue. Remember each person's own choice of that toggle, along with which Bitbucket account is theirs, so the filter works without them re-selecting themselves every morning.
Clicking a card opens a detail pane built from Get Pull Request for the full record including description, branches and reviewers, List Pull Request Commits for what is actually in the change, and List Pull Request Activity for the review history in order. Show the comments from List Pull Request Comments threaded in that pane so someone can read the discussion without switching tools.
From the detail pane I want three write actions. Post a review comment with Create Pull Request Comment. Add a checklist item with Create Pull Request Task, which is how we track follow-ups we do not want to block on. Attach another reviewer with Update Pull Request, which edits the reviewer list on an open pull request. After any of these, refresh that card so the counts on the board stay honest.
Add a nudge button on each card that sends the assigned reviewer a Slack direct message containing the pull request title and a link to it. Resolve the reviewer to a Slack account with Look Up User by Email using their Bitbucket email, open the direct message with Open a Conversation, then post it with Send a Message. Keep the tone light, and do not let the same person be nudged about the same pull request more than once a day.
Important: do not build approve, decline, or merge buttons into this app. The actual sign-off stays in Bitbucket. Instead give every card and the detail pane a prominent link straight to the pull request in Bitbucket, so the flow is read the board here, decide what to pick up, then jump over to approve or merge.
One performance note to design around: a workspace with many repositories, each with open pull requests that each need comments and tasks fetched, adds up to a lot of calls, and Bitbucket rate limits per hour. Load the board in as few round trips as you can, fetch comment and task counts efficiently rather than one card at a time where possible, cache the results for the session, and give the board a manual refresh button rather than re-fetching everything constantly.
What does this prompt do?
- Gathers every open pull request from all the repositories in your Bitbucket workspace onto one board, so nobody has to click into repos one at a time to find their reviews.
- Sorts them into columns for waiting on review, changes requested, and approved but not merged, grouped by the person who owns the review.
- Shows how long each pull request has been sitting in business days, how many comments it has collected, and how many checklist items are still unticked, flagging anything past two business days in red.
- Lets you leave a comment, add a checklist item, pull in another reviewer, or send a teammate a private Slack nudge without leaving the board.
What do I need to use this?
- A Bitbucket Cloud account with access to the workspace whose repositories you want on the board
- A Slack workspace, if you want the nudge button to send direct messages to reviewers
- Your teammates' Slack email addresses matching the ones on their Bitbucket accounts, so nudges reach the right person
How can I customize it?
- Change the red flag threshold from two business days to whatever review turnaround your team promises
- Choose which repositories or workspaces feed the board, so busy teams can hide archived or experimental repos
- Group the columns by pull request author instead of reviewer, or hide drafts so only review-ready work shows up
FAQs
Does this work with Bitbucket Cloud or with self-hosted Bitbucket?
Can I approve or merge a pull request straight from the board?
Will it really show pull requests from every repository?
Can each person see only the reviews assigned to them?
Do the Slack nudges get posted somewhere public?
Related templates
See how your brand's news coverage and sentiment stack up against four competitors, then let an assistant write the weekly report for you.
One screen showing every social post waiting on approval, sorted by deadline, so reviewers can approve or reject without leaving the page.
Every Monday, find the past champions and closed-won contacts who changed jobs, update Attio, and get the moves worth chasing in Slack.
Staff submit what happened, your social manager edits the copy, picks the accounts and puts it on the calendar without a single spreadsheet.
Open one board each morning, see which voice calls went badly, replay the exact moment the caller got frustrated, and file the fix.
A personal queue of every overdue Guru card, sorted by how late it is, with one-click verify, reassign, comment, and an agent that drafts the refresh for you.
Stop clicking through repos to find your code reviews.
Open one board each morning and see exactly which pull requests are waiting on you and which ones have gone stale.