Daily Slack standup digest from yesterday's GitHub PRs
Every weekday morning, post a Slack summary of the pull requests your team opened, reviewed, and merged the previous day.
GitHub
Slack BotEngineeringOperationsDaily DigestsAI ReportsNotifications & AlertsBuild me an agent workflow that posts a daily engineering standup digest to Slack every weekday at 8:45am in my workspace timezone, summarizing the previous business day's pull request activity from GitHub.
On each run the agent should:
1. Use GitHub to list pull requests that were opened, reviewed, or merged during the previous business day across the repositories I configure. On Mondays, treat "previous business day" as the prior Friday so weekend gaps don't produce empty digests. Use the GitHub search and pull request listing operations and filter by updated_at, merged_at, and review timestamps.
2. Group the results into three sections: Merged, Opened, and In review (still waiting on a review or with requested changes). For each PR include the title, the author, the repo, a link to the PR, and a one line summary of what changed. Call out PRs that are older than three days without a review as stale.
3. Use the Slack bot to post a single message to the standup channel I configure. Format the digest in Slack markdown with bold section headers and clickable PR links. If there was no activity at all, post a short "quiet day on the PR queue" note instead of a long empty digest.
Inputs I want to be able to set when I install the workflow:
- The list of GitHub repositories or the GitHub organization to scan.
- The Slack channel name or ID to post into.
- Optional list of GitHub usernames or a team to restrict the digest to.
- The post time and timezone, defaulting to 8:45am workspace local time, weekdays only.
Use the GitHub integration for all repository and pull request reads, and the Slack bot integration to send the message. Keep the digest concise so it fits in one Slack message without truncation.
What does this prompt do?
- Scans your GitHub repositories every weekday morning for PR activity from the previous business day.
- Groups the activity into opened, reviewed, and merged so the channel can read it like a team status update.
- Calls out PRs that are still waiting on review, stale, or blocking a release.
- Posts the digest as a single Slack message to your standup channel before the team logs on.
What do I need to use this?
- A GitHub account with access to the repositories you want to track.
- A Slack workspace with the General Input Slack bot installed and added to the standup channel.
- The repository names (owner/repo) or the GitHub organization you want to include.
- The Slack channel name or ID where the digest should be posted.
How can I customize it?
- Change the schedule to run at a different time, only on certain days, or skip holidays.
- Narrow the scope to a single repo, a label, a team, or a list of GitHub usernames.
- Adjust the message format: switch to bullet lists, add emoji per status, or tag PR authors by Slack handle.
FAQs
What counts as yesterday's activity?
Do I need to list every repository by hand?
Will the bot post in private channels?
Can I send the digest as a DM instead of a channel message?
What happens when there are no PRs from yesterday?
Related templates
When someone leaves, we check which shared passwords they used in their final months and post a ranked rotation list to your security channel.
Every Monday, check every S3 bucket for public exposure, missing encryption and weak backup settings, then get the risks ranked in Slack.
Twice every weekday, the conversations from your social inbox land on the right HubSpot contact timelines, with a Slack recap for sales.
Every morning, find the addresses that hard bounced or filed a spam complaint, update the matching HubSpot contacts, and post a short Slack recap.
Every weekday at 4pm, spot the threads that went quiet, stage a ready-to-send nudge in your mailbox, and get a ranked Slack recap.
When you merge a fix in GitHub, this agent checks the matching dead-letter queue, replays the failed messages, and reports back on the pull request and in Slack.
Stop hand writing your standup updates.
Connect GitHub and Slack once, and Geni posts yesterday's PR activity to your standup channel every weekday morning.