read one github pull request before the next decision

walk into standup knowing what the pr does. paste the github link and a bot reads the pull request into plain words.

by the dusk bot team · checked 12 november 2026 · how we made this

the link gives it the repository owner, name and request number. you get the returned details without changing the pr. fetch changed files, reviews and test results separately when you're deciding whether to merge.

pixel art: a sky blue pixel bot and a mint pixel bot beside the GitHub mark on a white tile, a magnifying glass and a notebook, on a lemon field in front of chalk cliffs by the sea, one saying "read this pull request"

what it does

get the point of the pr before opening another tab. this action reads a known pull request. the bot takes the owner, repository and number from its link. it goes straight there rather than searching for a likely match.

ask what changed, why the author wants it and whether the pr is still open. use separate reads for changed files and reviewer comments.

when you would use it

walk into standup knowing what the pr does. paste the link, get three plain lines.
spot a pr that changed overnight. ask for the current title, status and description beside yesterday's summary.
bring a non-coding teammate along. ask for a plain explanation of the proposed change.

try it

paste this into a chat with your bot

every weekday at 12, read pull request 58 in plumtree/harbor-kit while it remains open. tell me what it proposes and tell me if the title, status or description changed since yesterday. say which details you could not read. keep it read only. when it closes, tell me once and ask me to pause this routine.

when: weekdays at 12:00, while the pull request stays open
needs: github connected with read only access to plumtree/harbor-kit

what comes back looks like this (an example)

plumtree/harbor-kit #58
pull request: simplify the address form
status: open
this summary covers the pull request record.
files, reviews and test runs need separate reads.

set it up

connect github as read only. include the repository you need.
paste the pull request link. ask the bot to confirm which pull request it found.
ask your question. request files or reviews separately if the decision needs them.
if you're following it daily, set the routine. pause it when the pull request closes.

what it needs from you

input	required	what it is
`repo`	yes	The name of the repository, without the .git extension.
`owner`	yes	The username of the account that owns the repository.
`pull_number`	yes	The number that identifies the specific pull request.

from composio's catalog for GitHub (action GITHUB_GET_A_PULL_REQUEST, read 12 november 2026⁴). your bot fills these in from what you tell it.

how dusk bot handles it

dusk bot counts Get a pull request as a read: it looks and changes nothing. a bot you allow only to read can use it.

the permissions GitHub asks for to run it: repo.

where it stops

a number alone isn't enough. request 58 in another repository is different work.
merge decisions need the files, reviews and tests. this action reads the pull request details; it doesn't collect that evidence or run code.
a correct link doesn't grant access. your connected github account must be able to open private repositories.

try it in 2 minutes

connect github with read only access
copy one pull request link
ask for the pull request in three lines
ask which files, reviews and test results you still need

before making the call

the link points to the right repository
the summary names the pull request
you have the changed files when the decision needs them
reviews and tests need their own evidence

mistakes people make

asking about '#58' without a repository

paste the full link. numbers repeat across repositories.

reading 'open' as 'ready to merge'

look at files, reviews and test results before deciding.

questions

can i give it just the pull request url?

yes, use the normal github link. the bot takes the owner, repository and number from it. you don't need to copy those parts separately.

will checking it also approve or merge it?

no. this action only reads. keep the bot read only when its job is to explain pull requests.

sources

dusk bot docs: files and apps
dusk bot docs: routines
dusk bot docs: a bot's computer
composio, GitHub toolkit (catalog version 20261104_00), 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].