write the github issue comment that moves things along

get the missing detail without writing another follow-up yourself. the bot reads a github issue or pull request and drafts a markdown comment.

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

paste the discussion link so it lands in the right repository. comments count as sends. they ask by default, and you can set a daily amount for the bot.

pixel art: a cyan pixel bot and a yellow pixel bot beside the GitHub mark on a white tile, two chat bubbles and a key with a tag, on a lilac hill in front of a calm sea with one small island, one saying "review before commenting"

what it does

a good question gets the reporter unstuck. paste the issue or pull request link. it gives the bot the account, repository and number. have it read the discussion so it asks for what's still missing.

this adds a new discussion comment. editing an old comment and reviewing specific code lines need other actions.

careful with Full access: a bot there with no sending rule can send up to 25 a day without asking. give it Ask every time.

when you would use it

ask for the missing step. review the question before the reporter sees it.
share a confirmed workaround. help people waiting on the issue without promising a release.
follow up on a pull request. leave a general comment when a line-by-line review is unnecessary.

try it

paste this into a chat with your bot

when a new issue opens in fernwharf-labs/relay, read it and its discussion. if the device model is missing, draft a short question asking for it. show the issue link and question here. post only after i allow it, then confirm here.

never promise a fix date or close the issue. if the reporter already gave the model, stay quiet.

when: when a new issue opens in fernwharf-labs/relay
needs: github read and write for reading and commenting; sending set to Ask every time

what comes back looks like this (an example)

fernwharf-labs/relay #68

question for lior: which device model has the connection drop?

open the linked issue, read the question, then choose **Allow** or **Deny**.

set it up

allow only the work it needs. connect github with reading and commenting actions for this bot.
set the send rule. choose Ask every time.
start with one issue link. ask for a comment based on the discussion, with no extra promises.
read it where it will land. confirm the repository and question, then choose Allow. early event runs appear in automations.

what it needs from you

input	required	what it is
`body`	yes	Comment content in GitHub Flavored Markdown.
`repo`	yes	Name of the repository (without `.git` extension); not case-sensitive.
`owner`	yes	Account owner of the repository (username or organization); not case-sensitive.
`issue_number`	yes	Number identifying the issue or pull request for the comment.

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

how dusk bot handles it

dusk bot counts Create an issue comment as a send: it reaches people or moves money, so it waits for your Allow (unless you set a daily amount, or the bot is on Full access with no sending rule, which lets it send up to 25 a day). a bot you allow only to read can never call it.

the permissions GitHub asks for to run it: repo, public_repo.

where it stops

issue numbers repeat across repositories. use the full link with the owner, repository and issue number.
people can read what you post. remove private customer details even if they helped the investigation.
use a general comment for discussion. a fix still needs code, and a formal code review needs its own action.
events arrive at once; sleeping bots cannot act. local work needs the computer awake and the app open. dusk cloud stays on.

try it in 2 minutes

paste one github issue link
ask it to read the thread
ask for a question in your dusk chat
confirm the repository before allowing the post

mistakes people make

asking it to comment on just #68

paste the full link. issue numbers repeat in other repositories.

turning a guess into a release promise

ask only for missing facts. keep dates out until someone confirms them.

questions

can it comment on a pull request too?

yes. paste its link and ask for a general discussion comment.

can every comment wait for me?

yes. set sending to Ask every time. each comment then comes to you with an approval card.

sources

dusk bot docs: files and apps
dusk bot docs: routines
dusk bot docs: computer permissions
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].