Stuck PR alerts in Slack, every morning
GitLoom is a Slack-first pull request notification tool that watches your GitHub repos and posts one quiet morning digest of every stuck PR: waiting on a first review, approved but unmerged, blocked by a merge conflict, failing CI, or small and forgotten.
If nothing is stuck, it stays silent. One quiet digest, not forty notifications.
Good morning. 4 pull requests need a nudge across 3 repos:
Waiting on first review: api#482 Add rate limiting to webhook delivery (Priya)
Opened Monday, still no first review. Marcus touched this code last.
Approved, not merged: billing#517 Migrate billing webhooks to v2 (Jonas)
Sara approved it two days ago. One click from shipping.
Merge conflict: web#495 Refactor session storage (Ale)
Conflicts with main since yesterday’s auth merge. Needs a rebase.
Failing CI: api#490 Upgrade the payments SDK (Marcus)
CI has been red since yesterday: two unit tests. Green checks are all that stand between this and merge.
Everything else is moving normally. Nothing else needs you today.
One quiet digest, not forty notifications.
Pull requests do not fail loudly. They just sit.
Every team has them. The PR that has been waiting on review since Tuesday. The one that got approved and then never merged. The branch quietly rotting in a merge conflict while main moves on. The check that went red on Friday and stayed red. Nobody decided to ignore them; they just fell out of everyone’s working memory.
GitHub does not surface any of this. The official Slack app announces every push, comment, and status check until someone mutes the channel, and once the channel is muted, the one notification that mattered disappears with the rest. GitHub’s own PR list shows what is open, not what is stalled.
So catching stalled PRs becomes somebody’s job. A lead scanning open PRs before standup. Authors posting “can someone take a look?” and feeling like they are nagging. It works until the week gets busy, which is exactly when pull requests get stuck.
Waiting on a first review
The author asked once, did not want to ask twice, and moved on to the next branch. The PR ages quietly while everyone assumes someone else will pick it up.
Approved but never merged
The hard part is done. Then a deploy freeze, a weekend, or a closed tab, and work that was one click from shipping never ships.
Blocked by a merge conflict
Main moved and the branch did not. Every day of waiting makes the rebase bigger and the author less eager to do it.
Small and forgotten
Ten-line fixes are the easiest reviews and the first to fall through the cracks, because nothing about them ever feels urgent.
Every stalled PR, surfaced while it still matters
On weekday mornings, GitLoom checks your repos and posts one message to the channel you chose. Each stuck PR gets a line in plain English: what it is, why it is stuck, and who can unblock it.
Catches every way PRs get stuck
Waiting on a first review, approved but unmerged, blocked by a conflict, failing CI, or small and forgotten. If a pull request stalls, it makes the list.
Quiet by default
If nothing new is stuck, GitLoom posts nothing. WIP and blocked labels are respected, and a bot approval never counts as a review. Silence is a signal too: it means everything is moving.
Batched reminders, not nagging
A PR that stays stuck is re-mentioned every few days, not every morning. Reminders keep their weight and the channel stays readable.
Plain English, not event payloads
Each line reads like a teammate wrote it. No JSON, no bot-speak, no wall of links: just the PR, the reason, and the next step.
Lands where the team already reads
Slack first, with email and Telegram delivery for teams that live elsewhere. Nobody has to adopt a new tool to see it.
No dashboard to remember
The report comes to you on schedule, with PR state re-fetched from GitHub at send time so it never lists a PR that already merged. Nothing to check, refresh, or remember to open before standup.
Stuck PR alerts in about two minutes
No YAML, no webhooks to wire up, no bot commands to memorize. Three steps and the first digest is on its way.
Install the GitHub App
Grant the repos you want watched. They are tracked automatically, and your code never leaves GitHub.
Connect Slack
Authorize GitLoom in your workspace. It only posts to the channels you pick; it never reads channel history.
Pick a channel
Turn on the Stuck PRs report and choose where it posts. From then on, stuck PRs show up on weekday mornings without babysitting.
Stuck PR alerts, answered
How GitLoom decides a pull request is stuck, and why the channel stays quiet.
Your GitHub channel can stay muted.
Or tomorrow at 9:00 AM, every stuck pull request is one quiet Slack message away.
Two minutes to install · 14 days free · Quiet by default