Post a PR summary to Slack before code review
Summarize a pull request and post it to Slack so reviewers have context before they start
Overview
Reviewers often open a PR cold, spending the first few minutes figuring out what they're looking at. This template writes a summary that tells them what changed, why, and where to focus—posted to Slack so they have context before they even click the link.
How it works
- Fetches the open pull request by title from your specified repo
- Reads the diff and any existing PR description
- Writes a 3-5 sentence summary covering what changed, why, and review focus areas
- Checks if the PR has been open longer than your specified threshold with no reviewer assigned
- Posts the summary to Slack with a link to the PR
Who this is for
Tech leads and senior engineers who want reviewers to have context before starting a code review, without writing detailed summaries manually.
Suggested prompt
Fetch the open pull request titled [1. PR title] in [2. Repo name]. Read the diff and any existing PR description. Write a 3-5 sentence summary covering: what changed, why, and what the reviewer should pay most attention to. Post the summary to the [3. Channel name] Slack channel, with a link to the PR. Only post if the PR has been open for more than [4. Hours] hours and has no reviewer assigned yet.
Frequently asked questions
Can I skip the time and reviewer check?
Yes, remove those conditions from the prompt to post immediately for any open PR.
Can I post to a different channel per team?
Yes, modify the prompt to route summaries to different channels based on the PRs labels or affected files.
What if I use GitLab instead of GitHub?
Swap GitHub for GitLab in the prompt and connect GitLab to your MCP server.
Can I include the full diff in the summary?
Yes, but for large PRs its better to highlight key files; adjust the prompt to specify what to include.