GitHub PR Desk

One weekday digest of every PR, issue and comment across your repos

Summary excerpt from the creator’s share page. Not independently tested.

Open on x.ai and add to Grok BotOriginal post ↗Report a problem

What the share page says

Your morning GitHub desk. Every weekday it sweeps the repos you choose for new PRs, issues, and comments, sends one short digest, and gives each PR a merge, request changes, or close verdict. It never merges without your yes and drafts every public comment for your approval.

Description as published on the x.ai share page when last checked (2026-11-15).

What its description mentions

Read automatically from the creator's own words and quoted below. Not a test: check the Bot's skills and routines before relying on any of it.

Apps it names
GitHub
Sends messages
…it sweeps the repos you choose for new PRs, issues, and comments, sends one short digest, and gives each PR a merge, request changes, or…
Recurring work
Every weekday it sweeps the repos you choose for new PRs, issues, and comments, sends one short digest, and gives each PR a merge, request…
Promised limits
It never merges without your yes and drafts every public comment for your approval
Our take

Editorial notes

From the public description, not a test. Written by Grok Bot Wiki from the share-page text; we have not run this Bot. Reviewed .

Best for

A developer or small team that wants one short weekday rundown of what changed across a chosen set of repositories, with an opinion on each pull request, instead of opening every tab by hand.

Not for

Anyone who wants pull requests merged or comments posted automatically, since its description has every action waiting on an explicit yes.

What it does

Every weekday it sweeps the repositories the owner has named for new pull requests, issues and comments, and rolls the result into one short digest rather than a feed of separate notifications. For each open pull request it gives a plain verdict — merge, request changes, or close — so the owner can scan the reasoning instead of re-reading the diff from scratch. Any public comment it would post is drafted first and waits for approval, and the same holds for a merge; neither happens on its own.

First messages to try

  1. Watch these three repositories for me and start sending the weekday digest tomorrow morning.
  2. Give me your verdict on the open pull requests in the main repo right now, and say why for each one.
  3. Draft a review comment on PR 142 flagging the missing test coverage, but don't post it yet.

Apps and accounts

Its description mentions the repositories the owner chooses as its only source, read through GitHub; it names no other outside service.

Cautions

  • A merge, close, or public comment always waits for a yes, so treat its verdicts as a starting read, not a decision already made.
  • It only covers the repositories named to it, so a repo added later needs to be told to it explicitly before it shows up in the digest.

Compare with: PR Reviewer by MustafaRepo Monkey by KeranikEngineering QA by Andre Leibovici

Before you add it

Specific to this Bot, from what its description says:

  • The description says it sends messages. If that reaches anyone or anything besides you, set an ask-first rule for it before the first run.
  • It describes recurring work. After adding it, open its routines, confirm the times, and pause any schedule you did not choose.
  • It names GitHub. Connect those as plugins where one exists rather than signing in through the shared browser, and give it the narrowest access the task needs. What to check for GitHub ↗
  • Its description makes a promise about limits. Confirm it in the Bot's skills and rules before relying on it.
The standard checks for any shared Bot

Adding a shared Bot copies its profile, settings, enabled skills, routines, and avatar into your account. It does not copy the creator's computer, logins, conversation history, or memory. Everything it then does runs on your shared Agent Computer with your logins.

  • Open the Bot's skills and routines first. Disable any routine before it fires on a schedule you did not choose.
  • Check which apps it will try to sign into. Prefer plugins over browser logins, and keep sensitive accounts off the shared computer.
  • Set an ask-first rule for anything that sends, posts, pays, or deletes. A listing here is not a test result.
  • Give it one small bounded task and read the usage screen afterwards before scaling up.

Related reading: the shared computer permission boundaries the weekly meter

If it misbehaves: Bot not responding routines not running sign-in errors New to Grok Bot? what it is your first task

Attribution

This Bot belongs to its creator, Michael. Facts on this page (name, share link, creator, link status) were read from the public share page. The row was seeded from majiayu000/awesome-grok-bot, cs68614-hash/awesome-grokbot-templates, ZeroPointRepo/GrokBotDev and kydlikebtc/awesome-grokbot. Imported catalog prose retains CC BY 4.0 attribution; share-page excerpts are labeled separately. Grok Bot Wiki is independent and not affiliated with SpaceXSI (formerly xAI).

Made this Bot? Add a “Listed on Grok Bot Wiki” badge

Optional and free. It links readers to this page and never affects how the Bot is listed. More badge styles ↗

Markdown (README)

[![Listed on Grok Bot Wiki](https://www.grokbotwiki.com/badge/listed-dark.svg)](https://www.grokbotwiki.com/bots/github-pr-desk)

Or promote this template in the labelled Featured row, from $19.