The Slack AI assistant for your GitHub activity
GitLoom is a Slack-first pull request notification tool that watches your GitHub repos, posts one quiet daily digest of stuck PRs and shipped work, and answers questions about your GitHub activity when you ask in Slack.
“What shipped this week?” “Which PRs are waiting on me?” Ask in the channel your team already reads and get a plain-English answer drawn from your real GitHub activity.
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.
The morning digest, before anyone has to ask.
The answers live in GitHub. The questions live in Slack.
Every day someone asks a status question in Slack. Did the payments fix go out? Is anyone reviewing Priya’s PR? What is the release still waiting on? The answer exists, but it lives in GitHub, spread across PR lists, review threads, and merge timelines.
So an engineer stops what they are doing, opens GitHub, scans a few filtered views, pieces the story together, and types a summary back into Slack. Multiply that by every standup, every check-in, and every founder who just wants to know what shipped.
The official GitHub Slack app does not fix this. It forwards every push, comment, and review into a channel until everyone mutes it. A firehose of events cannot answer a question. It just moves the reading work from GitHub into Slack.
Status questions interrupt makers
Answering “where is that PR?” costs a context switch for the one person who knows. The asker waits, the maker loses focus, and the question comes back next week.
GitHub shows state, not the story
The PR list tells you what is open right now. It does not tell you what happened this week, what quietly stalled, or what has been approved and forgotten.
Event feeds get muted
Per-event notifications train everyone to ignore the channel. Then the one update that actually mattered scrolls past unseen.
Standups become status readouts
Fifteen minutes of reconstructing what happened since yesterday, when the whole picture could have been one calm message before the meeting.
Ask in Slack, answered from GitHub
GitLoom sits in your Slack workspace and watches your GitHub repos. Most days the morning digest already covers what changed. When you need more, ask GitLoom right in Slack and it answers from your real GitHub activity, no tab-switching required.
Plain English in, plain English out
Ask questions like “what shipped this week?” or “which PRs are waiting on me?” in Slack. Answers come from your team’s real GitHub activity, written as sentences, not a wall of links.
A digest that answers before you ask
On weekday mornings GitLoom posts one quiet digest: PRs waiting on a first review, approved but unmerged, stuck in merge conflicts, failing CI, or small and quietly forgotten.
Quiet by default
GitLoom speaks when something is stuck or when you ask it something. If nothing changed, it stays silent. Repeat reminders are batched so the channel stays readable.
Reports where your team already reads
Weekly digests, release notes, and stuck-PR reports land in the Slack channel you pick, and can also be delivered to email or Telegram.
No dashboard to babysit
There is no portal to remember to check. The whole product lives in the channel where the questions were already being asked.
Your code stays in GitHub
GitLoom works from pull request activity through the GitHub App you install, and reads only Slack messages that are addressed to it directly.
From install to first digest in about two minutes
No YAML, no webhooks to wire up, no syntax to memorize. Three steps and GitLoom is watching.
Install the GitHub App
Grant access to the repos you want GitLoom to watch. Repos you grant during install are tracked automatically.
Connect Slack
Add GitLoom to your workspace so it can post digests and reply where your team already talks.
Pick a channel
Choose where the digest lands. From then on GitLoom stays quiet unless something is stuck or someone asks.
Good questions, answered
Everything teams ask before pointing GitLoom at their repos and their Slack workspace.
Your team already asks in Slack. Now Slack can answer.
Install GitLoom, pick a channel, and tomorrow morning the first digest is waiting before anyone has to ask.
Two minutes to install · 14 days free · Quiet by default