Grok Bot and GitHub

GitHub 14 bots in the directory connect to GitHub, 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 GitHub

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.

Codebase Hardening Auditor
Audits a repo that shipped fast and returns ranked findings with file paths, line ranges, snippets, and a commit SHA, without touching a single branch.
Boundary: Never opens a pull request, pushes a commit, or edits a branch; findings land in a report you read.

Engineering Agent Manager
Tracks what every coding agent on your team is working on, what is blocked, and what two of them are quietly duplicating.
Boundary: Never merges, approves, or pushes to the default branch; it reports status and proposes moves for a human to make.

Help Center Updater
Watches merged pull requests for customer-visible changes and proposes help article edits, showing the current published text beside the rewrite.
Boundary: Never publishes, edits, or unpublishes a help center article; each change ships as current text beside proposed text for a human to paste.

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.

One Line Standup
Turns your day into a single honest sentence you actually keep, written from what changed rather than from what you meant to do.
Boundary: Never posts the summary anywhere, never shares it with a manager or a channel, and never keeps a streak or a score.

Persistent Bot Memory
Keeps one durable context file your other bots reread, admits only what belongs in it, and shows you every line before removing one.
Boundary: Never deletes or edits a stored entry without first showing the exact text and the reason; secrets and customer data never go in at all.

PR Review Sentinel
First-pass review on every new pull request with severity-tagged findings and a summary comment, before a human reviewer spends a minute.
Boundary: Never merges, approves, pushes, or requests changes; comments only.

Product Expert
Answers internal questions about how the product behaves today, with the doc, changelog entry, or merged pull request that proves it attached.
Boundary: Never speaks to a customer and never answers without a citation; an unsourced question comes back as not documented.

Standup Scribe
Drafts your daily standup from yesterday's commits, merged PRs, and calendar, delivered to your DM before the meeting.
Boundary: Posts only to your own DM, never to a shared channel.

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.

Support Ticket Fixer
Cleans the record around every arriving ticket, the type, the labels, the empty required fields, the wrong queue, the duplicates, and never the conversation.
Boundary: Never posts, edits, or sends a message in the ticket thread, and never closes, merges, or deletes a ticket on its own.

VM Overwatch
Housekeeps the shared Grok Bot computer, backs non-secret files on a weekday cadence, and files a weekly org review.
Boundary: Never deletes another bot's working files, never commits secrets, and never treats screens as isolation.

X Account Crew
A four-role crew that scouts, drafts, fact checks, and queues posts for one X account, and hands you a queue you release by hand.
Boundary: Never posts, replies, or schedules from your account; every draft waits in the queue until you copy it out and post it yourself.

Guides that cover GitHub

Grok Bot and GitHub: Permissions and What to Automate
Tutorial · A Grok Bot GitHub setup for PR triage, labels, and release notes, with the permission families to grant and the two actions it must never take: merge and force push.

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