Daily reminders for pull requests waiting on review
Your assistant builds a weekday check of your repos that finds pull requests open for more than a day without a review and posts them to your team's channel, tagging the requested reviewers.
- When
- Weekdays 9:30
- Uses
- GitHub, Slack
- 9:30✓ PRs waiting on review · SucceededLast run9:30 · 3 waiting
Can Claude remind my team about pull requests waiting for review?
Claude or another coding assistant can list open pull requests when you ask, but it won't check every morning by itself. With ClickRuntime connected, the assistant sets up a weekday automation that calls GitHub's API, finds pull requests waiting longer than your limit, and posts them to Slack with the reviewers named.
Why the assistant can’t do this on its own
- Nobody asks the assistant every morning; the point is that the reminder arrives without being asked.
- The check needs a GitHub token and a Slack connection that persist. ClickRuntime keeps both outside the chat.
- GitHub doesn't send an event for “still waiting”. Only a scheduled check can find it.
Set it up from your AI assistant
The same steps work in ChatGPT, Claude, Cursor and any assistant that supports MCP connectors.
- Step 1Connect ClickRuntime to your assistantAdd ClickRuntime as a connector (MCP server) in ChatGPT, Claude, Cursor or another MCP client, using https://clickruntime.com/api/mcp. You sign in with Google or email; there is no API key to copy. This is done once per assistant.
- Step 2Paste the promptStart a new chat and paste: “Create a ClickRuntime automation: every weekday at 9:30 Berlin time, find pull requests in acme/app and acme/api that are not drafts, have been open more than 24 hours and have no review yet. Post them to #eng in Slack with the title, age, author and requested reviewers. Post nothing if there are none.” Change the details (times, channels, addresses) to yours.
- Step 3Read the draftThe assistant restates what will happen, asks for anything missing, such as your timezone or which channel to post to, and saves a draft automation. A draft never runs on its own, so nothing happens until you agree.
- Step 4Connect accounts and save keysThe assistant asks you to save a fine-grained GitHub token with read access to pull requests on those repos as GITHUB_TOKEN in the ClickRuntime dashboard, and to connect Slack for notifications.
- Step 5Test itThe assistant runs it now and shows the message it would post, then turns the schedule on.
- Step 6Turn it onThe assistant tells you what will run, when, and which services it will contact, then asks your permission to turn it on. From then on it runs on ClickRuntime's servers, and you can close the chat.
- Step 7Check it in the ClickRuntime dashboardEach weekday run shows how many pull requests were waiting. Days with none post nothing. The schedule, next run times and the script are on the automation's page.
“Create a ClickRuntime automation: every weekday at 9:30 Berlin time, find pull requests in acme/app and acme/api that are not drafts, have been open more than 24 hours and have no review yet. Post them to #eng in Slack with the title, age, author and requested reviewers. Post nothing if there are none.”
Connector setup for each assistant: ChatGPT, Claude, Claude Code, Cursor, and other assistants.
What the assistant writes
A typical script for this job. Yours matches your pages, accounts and wording, and you can read every version in the ClickRuntime dashboard.
- A pull request counts as waiting when it's not a draft, older than 24 hours and has no review at all.
- Slack's <url|title> format makes each title a link.
- This is a report that does the same check every time, not a polling script, so it doesn't call report_fetched.
A schedule, not a trigger link
Use a schedule: weekdays at a time the team starts work. GitHub sends no event for a pull request that's simply waiting.
For a ping the moment a review is requested, add a trigger link for pull_request events as well (see the GitHub webhooks guide).
Limits
- The GitHub API returns up to 100 open pull requests per page; the assistant adds paging for busier repos.
- Slack usernames aren't GitHub usernames; map them in the script if you want real Slack mentions.
Troubleshooting
It reports pull requests that have reviews.
Reviews requested again after changes still count as reviewed in this version. Ask the assistant to treat “changes requested and updated since” as waiting.
A repo returns 404.
The token can't see that repo. Add it to the fine-grained token's repository list.
What you can add next
The first version is rarely the last. Because the automation is a Python script with memory, AI and any API available, you grow it by asking your assistant for the change. Each change is a new version, and a failed deploy never replaces the working one.
- Multi-step logic
Mention reviewers by their Slack handle
“Change my PRs waiting on review automation so it mentions reviewers in Slack using this mapping: octocat → @maya, hubot → @sam.”
- Built-in AI
Add a one-line AI summary of what each pull request changes
“Change my PRs waiting on review automation so each line includes a one-sentence summary of the pull request description.”
- Memory between runs
Escalate pull requests that appear three days running
“Change my PRs waiting on review automation so it remembers how many days each pull request has been listed and marks those on day three with ⚠️.”
- Any app or API
DM each reviewer instead of posting in the channel
“Change my PRs waiting on review automation so it sends each reviewer a direct message in Slack with only their pull requests.”
- Trigger links
Thank reviewers in the channel when a waiting pull request gets reviewed
“Add a GitHub webhook to my PRs waiting on review automation: when a listed pull request gets its first review, post a thank-you in #eng.”
- Schedules
A Friday summary of review times for the week
“Add to my PRs waiting on review automation: every Friday at 16:00, post the average time to first review this week per repo.”
Questions about stale pull request reminders
Does it work with GitLab or Bitbucket?
Yes, through their APIs. Save a token as a secret in the ClickRuntime dashboard and ask your assistant to read open merge requests or pull requests from that service instead of GitHub.
Can Claude check our pull requests every morning?
With ClickRuntime connected, yes. Claude sets up a weekday automation that checks GitHub and posts to Slack, without anyone opening a chat.
Does it need a GitHub app?
No. A fine-grained personal access token with read access to pull requests is enough, saved in the ClickRuntime dashboard.
Can it cover several repos or an organisation?
Yes. List the repos, or ask for every repo in the organisation that the token can read.
Does it work with GitLab?
Yes, through GitLab's API with a token saved as a secret. Ask your assistant for GitLab merge requests instead.
Other use cases
Scheduled tasks in ChatGPT and Claude
“Create a ClickRuntime automation: every weekday at 9, fetch yesterday's orders from our Shopify store and post the total to #sales in Slack.”
See the use case →Run code every hour
“Create a ClickRuntime automation: every hour, check our public API's /health endpoint and Slack #alerts if it returns anything but 200.”
See the use case →Webhook automation
“Create a ClickRuntime automation: when someone submits our Typeform, add their answers to a message in #leads.”
See the use case →Cron jobs without a server
“Create a ClickRuntime automation: every night at 2am UTC, call POST https://api.example.com/tasks/reindex with my ADMIN_TOKEN and email me if it doesn't return 200.”
See the use case →AI agent automations
“Create a ClickRuntime automation: every morning at 8, summarize new GitHub issues labelled 'bug' on our repo and post them to #eng.”
See the use case →Monitoring and alerts
“Create a ClickRuntime automation: every 5 minutes, check https://api.example.com/health and Slack #oncall if it fails twice in a row.”
See the use case →Stateful automations
“Create a ClickRuntime automation: every hour, check this product page and email me only when the price drops below the lowest price you've seen.”
See the use case →AI triage and summaries
“Create a ClickRuntime automation: every 15 minutes, label new support emails as billing, bug or other and post billing ones to #billing.”
See the use case →Website change alerts
“Create a ClickRuntime automation: every hour, check https://acme.com/pricing. Only look at the pricing table, not the whole page. When it changes, email me a short summary of what changed. Don't email me when nothing changed.”
See the use case →Price drop alerts
“Create a ClickRuntime automation: every 2 hours, check the price on https://shop.example.com/products/monitor-27. Email me when it drops below $280. Tell me only once per drop, and include the lowest price seen so far.”
See the use case →Uptime checks
“Create a ClickRuntime automation: every 5 minutes, check https://app.example.com/health. It's down if the status isn't 200, it takes longer than 5 seconds, or the body doesn't contain "ok". After 2 failures in a row post to #ops in Slack, and post again when it's back up with how long it was down.”
See the use case →RSS feed alerts
“Create a ClickRuntime automation: every 30 minutes, check https://www.postgresql.org/news.rss. Post each new item to #eng in Slack with its title, link and a one-line summary. Never post the same item twice. On the first run, don't post old items.”
See the use case →Job post alerts
“Create a ClickRuntime automation: every 2 hours, check the Greenhouse job boards for the companies acme and betaco. Email me new jobs that are product design roles open to remote work in Europe. Include title, location and link. Never send the same job twice.”
See the use case →Brand mention alerts
“Create a ClickRuntime automation: every 30 minutes, search Reddit and Hacker News for "Acme CRM". Post each new mention to #mentions in Slack with the title, link and a label: question, complaint, praise or other. Never post the same thread twice.”
See the use case →Daily Slack message
“Create a ClickRuntime automation: every weekday at 9:00 Europe/Berlin, post to #team in Slack: a good-morning line, the number of open issues labelled Bug in our Linear team ENG, and the 3 oldest ones with links.”
See the use case →Daily news digest
“Create a ClickRuntime automation: every day at 7:30 Europe/London, collect new items from these feeds: <feed URLs>. Pick the 5 most important for someone following AI policy in the EU, and email me a digest with a two-sentence summary and link for each. Don't include anything I was sent before.”
See the use case →Weekly metrics to Google Sheets
“Create a ClickRuntime automation: every Monday at 7:00 America/New_York, add a row to the KPIs tab of my sheet “Company metrics” with the week start date, last week's Stripe revenue (succeeded charges minus refunds), number of new customers and number of refunds.”
See the use case →Morning briefing
“Create a ClickRuntime automation: every weekday at 7:00 Europe/Lisbon, read today's events from my work Google Calendar, get today's forecast for Lisbon, and email me a short briefing: the weather in one line, each meeting with time and who's in it, what I should prepare, and my free blocks of 30 minutes or more.”
See the use case →Slack channel summary
“Create a ClickRuntime automation: every weekday at 17:30 America/Chicago, read today's messages and thread replies in #product, and post to #product-digest a summary with three parts: decisions made, open questions, and action items with who owns them.”
See the use case →Inbox summary each morning
“Create a ClickRuntime automation: every weekday at 7:30 America/Los_Angeles, read the emails that arrived in my Gmail inbox since the last summary. Email me a summary in three groups: needs a reply, FYI, and newsletters or notifications. One line per email with the sender. Skip anything I already read.”
See the use case →Form submissions to Google Sheets
“Create a ClickRuntime automation: when someone submits my Typeform contact form, add a row to the Leads tab of my Leads spreadsheet with the date, name, email, company and message. Check the Typeform signature so only real submissions are added.”
See the use case →Form leads to your CRM
“Create a ClickRuntime automation: when my website form posts a lead (name, email, company, message), create or update the contact in HubSpot by email, set lifecycle stage to lead, and add the message as a note on the contact.”
See the use case →Handle Stripe webhooks
“Create a ClickRuntime automation: when Stripe sends checkout.session.completed, post the customer email and amount to #sales in Slack. Check the Stripe signature and handle each event only once.”
See the use case →React to GitHub events
“Create a ClickRuntime automation: when a new issue is opened in acme/app, read the title and body and add one label: bug, feature or question. Check GitHub's webhook signature.”
See the use case →Sort Gmail automatically
“Create a ClickRuntime automation: every 15 minutes, look at new messages in my Gmail inbox and add one label: Invoice, Customer, Newsletter or Needs reply. Email me straight away when a customer message sounds urgent.”
See the use case →Recurring reminders
“Create a ClickRuntime automation: on the last weekday of every month at 10:00 London time, post “Reminder: send this month's invoices” to #finance in Slack.”
See the use case →Scheduled social posts
“Create a ClickRuntime automation: every 15 minutes, read my Post queue sheet (columns: When, Text, Status). Publish each row whose When has passed and whose Status is empty to my LinkedIn profile, then set Status to the post link.”
See the use case →Sync data between apps
“Create a ClickRuntime automation: every 30 minutes, find records in my Airtable Customers table that changed since the last run, and create or update the HubSpot contact with the same email, copying name, company and plan.”
See the use case →Summarise customer feedback
“Create a ClickRuntime automation: every Monday at 9:00, read the rows added to my Feedback sheet since last time (columns: Date, Source, Text), group them into up to 6 themes with a count and one short quote each, and post it to #product in Slack.”
See the use case →Daily standup in Slack
“Create a ClickRuntime automation for our async standup: every weekday at 9:30 Berlin time, post “Standup: what did you do yesterday, what's next, anything blocking?” in #team. At 12:00, read the replies in that thread and post a short summary in the thread, listing blockers first and who hasn't replied.”
See the use case →
Set up your first automation in ChatGPT or Claude
Free plan. No credit card.