Pull request reminders in Slack your team won't mute
GitLoom is a Slack-first pull request notification tool that replaces per-event review pings with one quiet weekday digest: which PRs are waiting on review, which are approved but unmerged, which are failing CI, and which have quietly stalled.
If a PR stays stuck, GitLoom brings it up again a few days later instead of nagging daily. And when everything is moving, it says nothing at all.
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.
Per-event reminders train everyone to mute the channel
You set up pull request reminders because PRs were sitting unreviewed. The usual fix makes it worse: the official GitHub Slack app posts on every open, comment, push, and review, and within a week the channel is wallpaper. People mute it, and the PRs sit even longer than before.
GitHub's built-in scheduled reminders (the feature it kept from Pull Panda) were a real step forward. They post a list of pull requests waiting on a team's requested reviewers, on a schedule you pick. For a single team that only needs review-request nudges, they can be enough.
But they are built around review requests. With the default filters, a PR that was approved three days ago and never merged is easy to filter out or lose in a list of bare links. Nothing flags one blocked on a merge conflict, one sitting on a red check since Friday, or the twelve-line fix nobody was ever asked to review, and nothing explains why any of them is stuck. And when the same PR appears in the same list every morning, the list gets skimmed, then ignored.
Per-event pings get muted
Every comment and push becomes a notification. The channel that was supposed to surface stuck PRs becomes the channel everyone silences.
Review requests are only part of the story
Scheduled reminders cover PRs waiting on a requested reviewer. Approved-but-unmerged work, merge conflicts, failing CI, and forgotten small PRs slip through.
Daily repeats become wallpaper
A reminder that fires every day for the same PR stops registering by day three. Repetition without change reads as noise.
Bare links get skipped
A list of PR links says nothing about why each one is stuck or what would unblock it, so acting on it takes work nobody does at 9 AM.
One quiet digest on weekday mornings
GitLoom watches your repos and posts a single message to the channel you pick. Each line names a stuck PR, says why it is stuck, and points at the next action.
Every kind of stuck, not just review requests
The digest covers PRs waiting on a first review, approved but never merged, blocked by a merge conflict, failing CI, and small ones that fell through the cracks.
Repeat reminders are batched
If a PR stays stuck, GitLoom does not nag daily. It brings the PR up again every few days, so a reminder still means something when it arrives.
Silent when nothing is stuck
No message on a clean morning. The channel only hears from GitLoom when something actually needs a nudge, which is why it stays unmuted.
Plain English, with context
Each reminder is a sentence, not a bare link: who opened the PR, how long it has waited, and what would unblock it.
One schedule, one message
Reminders land on weekday mornings as a single digest instead of a stream of real-time interrupts scattered across the day.
Slack first, email and Telegram too
The digest goes to the channel your team already reads. Teams that prefer email or Telegram can deliver there instead.
Set up in about two minutes
Install the GitHub App
Pick the repos GitLoom should watch. Repos you grant during install are tracked automatically, with nothing to configure per repo.
Connect Slack and pick a channel
Authorize the Slack app and choose where reminders should land. A channel the team already reads works better than a bot graveyard.
Get the first digest
Reminders arrive on weekday mornings from then on. If nothing is stuck, nothing is sent, and there is nothing to babysit.
Pull request reminders, answered
How GitLoom compares to GitHub scheduled reminders, what counts as stuck, and how batching keeps the channel readable.
One quiet reminder beats forty pings.
Tomorrow at 9:00 AM, one message lists every PR that needs a nudge. The rest of the day stays quiet.
Two minutes to install · 14 days free · Quiet by default