GitHub Steward

GitHub Steward runs GitHub for you from chat: it sets up one board of your work, keeps your folders private, makes changes as drafts, and asks before

Summary excerpt from the creator’s share page. Not independently tested.

Open on x.ai and add to Grok BotReport a problem

What the share page says

GitHub Steward runs GitHub for you from chat. It keeps one main board of your work plus a board for each app you build, keeps your folders private, makes changes as drafts, and asks before anything public, paid, or permanent. It needs the GitHub connector and works on the free plan. Loader: at the start of every run, load the steward-charter skill first.

Description as published on the x.ai share page when last checked (2026-11-15).

What its description mentions

Read automatically from the creator's own words and quoted below. Not a test: check the Bot's skills and routines before relying on any of it.

Apps it names
GitHub
Promised limits
It keeps one main board of your work plus a board for each app you build, keeps your folders private, makes changes as drafts, and asks…
Our take

Editorial notes

From the public description, not a test. Written by Grok Bot Wiki from the share-page text; we have not run this Bot. Reviewed .

Best for

Someone who wants a lightweight GitHub assistant for a personal or small project, run entirely from chat, that keeps changes private and reviewable rather than acting on its own.

Not for

A team that needs multi-repository board management across a whole organization, since the description frames this around one person's own work on the free GitHub plan.

What it does

It sets up a single board to track your GitHub work, keeps new repositories private by default, and proposes every change as a draft rather than committing it outright. Anything that would go public, cost money, or can't be undone, such as publishing a repository, deleting something, or spending on a paid plan, waits for an explicit yes first. The only times it sends you to github.com yourself are a handful of one-time steps, like creating an account and approving the connector, after which the day-to-day work happens back in chat.

First messages to try

  1. Set up a private repository for a side project called recipe-tracker and get me a board to track the work.
  2. Draft a pull request that adds a basic README to my project, but don't open it until I say go.
  3. What GitHub changes are still waiting on my approval right now?

Apps and accounts

Its description mentions needing the GitHub connector and says it is built to run on the free GitHub plan without requiring a paid upgrade.

Cautions

  • It's scoped to one person's own repositories on the free plan, so it's not a fit if you need it to coordinate work across a whole organization's repos.
  • Review each drafted change yourself before approving it, the same as you would with any other GitHub pull request.

Compare with: Cloudflare GitHub Site Bot by Roman LorenzenEngineer by Andrew KittridgeGitHub PR Desk by Michael

Before you add it

Specific to this Bot, from what its description says:

  • It names GitHub. Connect those as plugins where one exists rather than signing in through the shared browser, and give it the narrowest access the task needs. What to check for GitHub ↗
  • Its description makes a promise about limits. Confirm it in the Bot's skills and rules before relying on it.
The standard checks for any shared Bot

Adding a shared Bot copies its profile, settings, enabled skills, routines, and avatar into your account. It does not copy the creator's computer, logins, conversation history, or memory. Everything it then does runs on your shared Agent Computer with your logins.

  • Open the Bot's skills and routines first. Disable any routine before it fires on a schedule you did not choose.
  • Check which apps it will try to sign into. Prefer plugins over browser logins, and keep sensitive accounts off the shared computer.
  • Set an ask-first rule for anything that sends, posts, pays, or deletes. A listing here is not a test result.
  • Give it one small bounded task and read the usage screen afterwards before scaling up.

Related reading: the shared computer permission boundaries the weekly meter

If it misbehaves: Bot not responding routines not running sign-in errors New to Grok Bot? what it is your first task

Attribution

This Bot belongs to its creator, Lee Talley. Facts on this page (name, share link, creator, link status) were read from the public share page. The row was seeded from majiayu000/awesome-grok-bot, cs68614-hash/awesome-grokbot-templates and kydlikebtc/awesome-grokbot. Row metadata is CC0. Grok Bot Wiki is independent and not affiliated with SpaceXSI (formerly xAI).

Made this Bot? Add a “Listed on Grok Bot Wiki” badge

Optional and free. It links readers to this page and never affects how the Bot is listed. More badge styles ↗

Markdown (README)

[![Listed on Grok Bot Wiki](https://www.grokbotwiki.com/badge/listed-dark.svg)](https://www.grokbotwiki.com/bots/github-steward)

Or promote this template in the labelled Featured row, from $19.