Bot recipe · Engineering
Error summary.
Summarizes new errors in your error tracker with their stack trace and the likely commit, and posts it in your team chat.
Free: 30 answers a day, plus 300 trial credits for every other model. No card.
It starts
- On a schedule
- Every hour
It works with
-
GitHub
Any error tracker
-
Bugsink
Any team chat
-
Slack
-
Teams
-
Discord
-
Basecamp
Its changes
Posting asks as you; automatic as itself.
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 error tracker”. Change them before it starts, or any time after.
For each new issue in your error tracker, read the latest event's stack trace and the app's own frames. Find the last change to those lines in your code host. Write three lines: what broke, since when, and who touched it last. Post one message in your team chat per run, never one per event.
- Conversations
- A new conversation each run.
- Credits
- About 5 to 25 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.
-
Issue triage
Labels new issues in your issue tracker from your set, links duplicates, asks for what's missing, and otherwise stays quiet.
-
Pull request reviewer
Reviews each pull request against the repository's conventions and leaves one review, not a stream of nits.
-
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.
-
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 Error summary. Every part of it stays yours to change.
Free: 30 answers a day, plus 300 trial credits for every other model. No card.