Look into a slowdown after a release
The xAI docs show a bot looking into a slowdown after a release. It reads dashboards and traces and writes up the likely cause, keeping facts apart from guesses, before an engineer digs in.
Last verified: Oct 17, 2026
The problem
When an app slows down after a release, someone has to dig through dashboards and traces before the fix can start.
How the bot does it
From the official docs:
- The xAI docs give the example "Investigate the checkout latency increase since yesterday's release."
- The bot needs read access to your monitoring and analytics tools.
- The docs say it should separate facts from hypotheses and shouldn't change alerts or production settings.
Setup steps
- 1Connect your monitoring, tracing, or analytics tools with read access.
- 2Name the metric that got worse and the release it followed.
- 3Ask for a write-up with evidence links, facts kept apart from guesses.
- 4Tell it: Change nothing in alerts or production settings.
Example prompt
Investigate the checkout latency increase since yesterday's release. Use our dashboards and traces, separate facts from hypotheses, and link the evidence for each. Don't change alerts or production settings. Change nothing.
The result
A sourced write-up of the likely hotspot for an engineer to confirm and fix.
Templates on this page
Sources
Want new ones in your inbox?
Pick what you're into. We'll send the best new prompts and templates, plus the weekly robot show.
Related prompts
Design a 3D-printable replacement part from a photo
Users report sending a photo and a short description of a broken part and getting a CAD design, an STL file, and slicer settings back. You need your own 3D printer.
Here's a photo of [broken part] and its measurements. Draft a CAD design, export an STL I can 3D print, and suggest slicer settings. Tell me what to check for fit and strength. Change nothing else.
Keep your help center in sync with code changes
xAI's support post says its bot reviews code changes and suggests matching updates to the help center, so articles don't drift out of date.
Each day, review merged changes in [repo]. List any help center articles that are now out of date and draft the updates. Don't publish anything: I review and publish.
Monitor and debug your backend with the Supabase plugin
Use the Supabase plugin in Grok Bot to monitor, debug, and ship changes to your backend, with production changes kept behind approval.
Every morning, check my Supabase project for errors, failed functions, and slow queries. Report them with suggested fixes. Don't change anything without my approval.