Daily PR digest
One morning message to your team channel: PRs waiting on review, stuck, stale, and what shipped.
By DamonWorkflowVersion 10 installsUpdated Sep 30, 2026damon/workflow/daily-pr-digest
What it does
Every day at 9:00 the workflow checks the day and stops on weekends. On weekdays it reads the open pull requests in the repositories named in the agent step and groups them: waiting on review for over 24 hours (with the reviewer), no reviewer assigned, approved but not merged, failing checks, and no activity in 5+ days. It adds what merged in the last 24 hours, one line each. The digest (under 150 words, every PR linked) is saved to Engineering/PR digests/<date>.md in your drive and posted to your team's Slack channel. A copy opens as a chat thread in Damon for follow-up questions.
It never comments on, labels or merges a pull request.
What you need
- GitHub and Slack connected.
- The repositories and channel set in the agent step's instructions (defaults:
api,web,#eng).
Customize it
- Auto-approve
file.writeandmessage.sendfor this workflow so the digest posts without waiting on you; both require approval by default. - Change the thresholds (24 hours, 5 days) to match your team.
- Add a weekly workflow that turns the saved digests into release notes.
What it does, step by step
Step 1Trigger
Runs every day at 9:00 AM (America/New_York)Runs every day at 9:00; the agent step skips weekends.
Step 2Agent
If today is Saturday or Sunday, report "weekend, no digest" and stop. Repositories: api, web. Slack channel: #eng. List the open pull requests in those repositories and group them: (1) waiting on review for more than 24 hours, with the requested reviewer and how long it has waited; (2) no reviewer assigned; (3) approved but not merged; (4) failing checks, with which check and for how long; (5) no activity in 5 or more days. Then list pull requests merged in the last 24 hours, one line each. Name authors and PR numbers, link every pull request, no adjectives, under 150 words, headed "PR digest" with today's date. Save the digest to the drive as Engineering/PR digests/<YYYY-MM-DD>.md, then post it to the Slack channel. Never comment on, label, approve or merge a pull request. Return the digest.
UsesGitHub
Step 3Send a Message
Open a thread titled "PR digest" with today's date and post the digest from the previous step, noting that it was posted to Slack. On weekends, post one line saying no digest was sent.
What it connects to
What the agent reads and writes through each integration, and what stays with you.
What the agent can do with GitHub
- Reads
- Repositories, pull requests, reviews, checks and code in the repos you connect.
- Writes
- Branches and pull requests from coding tasks, and comments when a step posts one.
- Yours
- Nothing is merged unless a step merges it.
What the agent can do with Slack
- Reads
- Messages in the channels and threads the workflow names.
- Writes
- Messages to those channels when a step posts.
- Yours
- The agent posts only where the workflow points it; it does not join or create channels on its own.
