Skip to content

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.

Your assistantClickRuntime connected
Create a ClickRuntime automation: every weekday at 9:30, post to #eng any pull requests in acme/app waiting more than 24 hours for review.
I'll check open pull requests each weekday at 9:30, list those over 24 hours old with no review, and name the requested reviewers.
PRs waiting on reviewLive
When
Weekdays 9:30
Uses
GitHub, Slack
RunsClickRuntime dashboard
  • 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.

  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. Step 5Test itThe assistant runs it now and shows the message it would post, then turns the schedule on.
  6. 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.
  7. 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.
Prompt to copy.txt

“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.

stale_prs.pyexample
1from datetime import datetime, timezone
2from clickruntime import on_trigger, credentials, http, notify
3 
4REPOS = ["acme/app", "acme/api"]
5MAX_HOURS = 24
6 
7@on_trigger
8def run(event):
9token = credentials.secret("GITHUB_TOKEN")
10gh = {"Authorization": "Bearer " + token, "Accept": "application/vnd.github+json"}
11now = datetime.now(timezone.utc)
12lines = []
13for repo in REPOS:
14prs = http.get(f"https://api.github.com/repos/{repo}/pulls", headers=gh,
15params={"state": "open", "per_page": 100}).json()
16for pr in prs:
17if pr["draft"]:
18continue
19age = (now - datetime.fromisoformat(pr["created_at"].replace("Z", "+00:00"))).total_seconds() / 3600
20if age < MAX_HOURS:
21continue
22reviews = http.get(pr["url"] + "/reviews", headers=gh).json()
23if reviews:
24continue
25who = ", ".join("@" + r["login"] for r in pr["requested_reviewers"]) or "no reviewer set"
26lines.append(f"• <{pr['html_url']}|{pr['title']}> ({repo}, {int(age)}h, by {pr['user']['login']}) waiting on {who}")
27if not lines:
28return {"summary": "Nothing waiting"}
29notify.slack("Pull requests waiting for review:\n" + "\n".join(lines), channel="#eng")
30return {"waiting": len(lines)}
  • 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.”

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

Set up your first automation in ChatGPT or Claude

Free plan. No credit card.

Server URLhttps://clickruntime.com/api/mcp