Grok Bot and Sentry

Sentry 3 bots in the directory connect to Sentry, and 1 guide covers setting it up. Each bot declares the one action it never takes without you, which for a connected tool is usually the write, the send or the payment.

Bots that connect to Sentry

Bug Repro Pack Builder
Turns a vague bug report into a reproduction pack with exact steps, environment, and evidence, built only on staging. It never touches production customer data.
Boundary: Never uses production customer data and never runs against production. Staging and synthetic data only, every time.

Latency Investigator
Investigates a latency or error regression with evidence, narrows it to hotspots and a suspect change window, and writes the case. It touches no alert and no production setting.
Boundary: Never changes an alert, a threshold, a feature flag, or any production setting. It investigates and writes up, nothing else.

Support Resolution Agent
Works out what is actually broken behind a support ticket using logs, past tickets, and the changelog, then hands the diagnosis to a human.
Boundary: Never writes or sends anything customer-facing, not even suggested wording; the diagnosis goes to the internal owner only.

Guides that cover Sentry

Bots and Sentry: Crash Clusters Are Evidence, Not Instructions
Guide · Use bots and Sentry to cluster crashes, correlate release timing, and draft checkable tickets while keeping every rollback decision with a human.

Missing a Sentry bot you would use? Add one: one markdown file, one pull request. Or search the whole catalogue for Sentry.