Generate and post weekly code review summaries to Slack
Pull PR activity from GitHub and post a formatted summary to Slack
Overview
Tracking what got reviewed, merged, and left open means pulling data from GitHub and writing it up yourself. This template does both—organizing PR activity into a clear summary and posting it to Slack so your team stays aligned without the manual work.
How it works
- Pulls all PRs opened, merged, or closed in the past seven days from your repo
- Notes the title, author, status, and linked issues for each
- Organizes results into Merged This Week, Still Open, and Closed Without Merging
- Formats the summary for a dev audience—brief and factual
- Posts the summary to your specified Slack channel
Who this is for
Engineering leads and dev team managers who want weekly PR summaries posted to Slack without writing them manually.
Suggested prompt
Pull all pull requests from my GitHub repository [1. Repo name] that were opened, merged, or closed in the past seven days. For each PR, note the title, the author, the status (open, merged, or closed), and any linked issues. Organize the results into three sections: Merged This Week, Still Open, and Closed Without Merging. Then post a formatted summary to the [2. Channel name] channel in Slack. Keep the tone brief and factual—this is for a dev team, not an executive audience.
Frequently asked questions
Can I change the time window?
Yes, adjust past seven days to any interval that fits your review cadence.
Can I pull from multiple repos?
Yes, add more repo names to the prompt to aggregate PR activity across projects.
What if I want to post to a different tool?
Swap Slack for Microsoft Teams or Discord in the prompt and connect that app to your MCP server.
Can I include reviewer names?
Yes, modify the prompt to include who reviewed or approved each PR.