Bot recipe · Engineering
Issue triage.
Labels new issues in your issue tracker from your set, links duplicates, asks for what's missing, and otherwise stays quiet.
Free to start: 300 trial credits once, for every model. No card.
It starts
- New issues
-
Checked every minute in GitHub
-
As it happens in Linear
-
As it happens in Jira
-
Checked every hour in monday.com
- Every hour in the others
It works with
Any issue tracker
-
GitHub
-
Linear
-
Jira
-
Asana
-
monday.com
Its changes
Labels, comments, and closing each ask, unless you let it run.
Its instructions
What it's told, word for word.
The bot reads these on every run, with your own tools named where they say “your issue tracker”. Change them before it starts, or any time after.
Triage each new issue or comment in your issue tracker, the one that just came in or those since the last run; with nothing new, stop. Label it from the project's own labels, at most two. Link a duplicate only after reading it in full, and close it as one. Reply only when it helps (an answer from the docs, a released fix, one essential question, or a recap of a long report); otherwise stay silent. Close only what is plainly finished, saying why.
On GitHub, read the labels the repository has, search its issues and code with GitHub's search, check its releases, comment on the issue, and label or close it with GitHub's issue tools (a duplicate as a duplicate of the older issue). Never fetch the whole repository.
In Linear, also set the team and priority from the team's own, and leave workflow states to people.
In Jira, also set the component and priority from the project's own, and leave the workflow to people.
- Conversations
- One per issue where new issues start it; otherwise a new conversation each run.
- Credits
- About 3 to 15 credits a run, at the model's own rate.
- Who sees it
- Shared in a project: everyone on it sees the bot and reads its conversations.
Engineering
More recipes like it.
-
Pull request reviewer
Checks each pull request against your contribution rules, asks Copilot to review the ones that deserve it, and closes what your scope rules out, saying why.
-
Engineering standup
Writes your standup from what you did yesterday in your code host and your issue tracker.
-
Issue fixer on a computer
Turns an issue a maintainer labels into a draft pull request, running the tests on a computer the team lends it.
-
Error summary
Summarizes new errors in your error tracker with their stack trace and the likely commit, and posts it in your team chat.
-
Stale work nudger
Finds issues in your issue tracker nobody moved in two weeks, and asks whoever has them where they stand.
-
Answers from the code
Answers questions in issues and discussions from the repository's own code and docs, Copilot style.
-
Small fix pull requests
Turns an issue a maintainer labels into a small draft pull request, written from a copy of the code in the chat.
-
Release notes drafter
Drafts release notes in the style of the last two releases when a tag or draft release appears.
-
CI doctor
Explains why a pull request's CI failed and what to change, in one comment.
-
Flaky test hunter
Finds tests that fail and pass on the same commit across the week's CI runs, and keeps one issue up to date.
-
Dependency update reviewer
Reads each Dependabot or Renovate pull request's changelog and says whether it's safe.
-
Dependency upgrader on a computer
Upgrades outdated dependencies weekly, runs the tests, and opens one pull request.
-
Error noise keeper
Resolves the errors in your error tracker that the latest release fixed, and proposes muting known noise.
-
Stale pull request nudger
Lists pull requests waiting on review for more than two days, and who they wait on, in your team chat.
-
On-call handoff
Writes the weekly on-call handoff from incidents, errors, and open issues.
-
Security alerts digest
Summarizes Dependabot, code scanning, and secret scanning alerts across repositories, worst first.
-
Docs drift checker
After each merge to main, checks whether the docs still describe the code, and opens one issue when not.
-
Customer changelog writer
Turns each release into a customer-facing changelog entry in your docs.
Start from this recipe.
Sign up, open Bots, and pick Issue triage. Every part of it stays yours to change.
Free to start: 300 trial credits once, for every model. No card.