dusk bot
routinesgithub review reminder

dusk botroutines

see which github pull requests still need your review

find the pull requests where someone is waiting for you personally. a weekday reminder reads the current reviewer list in one github repository.

by the dusk bot team · checked · how we made this

it brings open requests with your handle to dusk chat, with the oldest pull request first. that gives you a review queue without another round of pings for the authors.

pixel art: a mint pixel bot, a purple pixel bot and a yellow pixel bot beside the GitHub mark on a white tile, an alarm clock and a calendar and a folder of papers, on a grassy meadow in front of little green islands on a lake, one saying "your review is due"

the message

paste this into a chat with your bot

at 10 am every weekday, list all open pull requests in the github repository orchardpress/catalog. my github handle is @owen-pike. skip drafts. for each remaining pull request, read its currently requested reviewers. keep exact matches to my individual handle. skip team-only requests.

put the results in this chat, oldest pull request first. include its number, title, author and opening date. say how many remain if the list runs past five. never submit a review, request another reviewer, comment or merge. stay quiet when the full list has no match. flag any reviewer list you couldn't read.
when
weekdays at 10 am, just before your review block
needs
github read only for open pull requests, their details and requested reviewers3. enter your repository and reviewer handle in the message.

what comes back

an example, not a real run

review queue · orchardpress/catalog
#84 · keep leading zeros on stock codes · opened nov 16 by calvin reed
#89 · align shelf labels on narrow paper · opened nov 19 by june park
both currently request your individual review.

make it yours

  • choose one base branch. limit the list to changes aimed at the release branch during a release week.
  • move the reminder next to review time. an afternoon slot works better if you write code through the morning.
  • include a team deliberately. name its exact handle and put team requests below personal ones.

when it goes wrong

  • an old pull request looks like an old request for review. keep the opening date labelled. it does not tell you when someone added you.
  • a request disappears overnight. open the pull request and read its current reviewers and state. it may have closed or someone may have removed your handle.

use the current reviewer list as your queue

a mention in a discussion can mean almost anything. a current review request gives you a concrete next step. the github connection can list the users and teams someone has asked to review.3

if you need a second pair of eyes immediately, ask a teammate directly. a morning list can wait almost a day.

questions

will this remind the author too?

the reminder belongs to you. it comes back to your dusk chat. the routine gives nobody else a notification.

what if i reviewed an earlier version?

follow the current request. if your handle appears again, include the pull request. an earlier review alone does not put it back on your list.

sources

  1. dusk bot docs: routines
  2. dusk bot docs: files and apps
  3. composio: github actions, checked 12 november 2026

drafted with ai help from the dusk bot docs and the sources listed on this page, then checked against them. if something here is wrong or out of date, write to [email protected].