ask ai to add the right labels to a github issue

give every keyboard bug the same label, without losing the labels already there. paste a github issue and the exact names to add. the bot keeps existing labels.

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

missing names become new labels, so a typo becomes part of your system. label changes bypass sending approval; put an ask-first instruction in the job if you want a preview.

pixel art: a sky blue pixel bot and an indigo pixel bot beside the GitHub mark on a white tile, a folder of papers and a signpost, on a grassy meadow in front of chalk cliffs by the sea, one saying "use the agreed labels"

where it helps

missing steps: add needs-reproduction after checking the report lacks them.
keyboard trouble: use your existing accessibility label for a navigation bug.
wrong component: add the agreed label for the affected part of the product.
another look: add a review label when the owner requests one.

the short version

make the next issue easier to find. paste its link, or describe it so the bot can find it. give your allowed labels and what each means.

use the owner, repository and issue number together. "acessibility" becomes a real label if it does not exist. the bot adds labels without removing the ones already there.

step by step

name your labels. connect github and give the bot the allowed spellings and meanings.
keep its reach small. allow read and write, limited to issue reads and label addition.
try one report. ask for the issue and proposed label before it changes anything.
open the issue. confirm the saved labels match your choice, then set the routine. pause it when label rules change.

send this to your bot

paste this into a chat with your bot

when a github issue opens in ticket-desk/box-office, read the report. propose access-check only for keyboard access problems. otherwise propose no label. show the issue number and the words supporting your choice here. ask me before you change anything. after i agree, add only access-check and report the saved labels. never create other spellings, remove labels or touch another repository.

when: when an issue opens in ticket-desk/box-office
needs: github read and write for this bot; allow issue reads and label addition in this repository

what comes back looks like this (an example)

ticket-desk/box-office #28
- reporter: hannah
- evidence: the date picker cannot be reached with the keyboard.
- proposed label: access-check

proposed addition: access-check. current labels will stay.

what can go wrong

your allowed list is the spelling guide. missing names become labels. keep the routine to the names you gave it.
use the full issue reference. the same number can belong to a different repository.
keep triage running overnight. github events arrive at once. dusk cloud keeps the bot working while your computer sleeps.

permissions and asking first

dusk bot counts Add labels to an issue as a change: it alters something in GitHub, and the sending setting does not cover it. a bot you allow only to read can never call it.

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

inputs

input	required	what it is
`repo`	yes	Repository name, without the `.git` extension (case-insensitive).
`owner`	yes	Username or organization name owning the repository (case-insensitive).
`labels`	yes	Array of label names to add to the issue.
`issue_number`	yes	Positive integer that uniquely identifies the issue within the repository.

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

try it in 2 minutes

paste one issue link
give the exact label name
ask for a proposal before any change
open the issue and read its labels

what it looks like

before

hannah reports a keyboard problem on issue #28. it currently has only bug.

after the bot

after your yes: bug and access-check. no extra spelling, no labels removed.

an illustration with made-up names and numbers.

mistakes people make

letting it invent labels

give it a short allowed list, with meanings.

recognising the title and skipping the repository

match the owner, repository and issue number.

questions

will this replace the labels already on the issue?

it adds to them. existing labels stay. tell it to add only the one you named.

what happens if the label does not exist?

github creates it. exact spellings prevent a collection of bug, bugs and bug-report labels.

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