Skip to content

Independent directorynot affiliated with xAI

Catalog refreshed Nobody pays to be listed or ranked

Grok Bot Templates
InspectLoading accountList your botList

Connector · 163 templates

Grok bots for GitHub

GitHub templates review pull requests, sweep notifications, scan for leaked secrets and write changelogs. Reading code is low-risk; pushing, merging and closing issues are not, so keep those decisions yours.

What GitHub access allowsSet it up safely

What it can access
Reads repos, opens pull requests and issues.
Say they ask first
21 of 163
Run on a schedule
50 of 163

Watch for: Read access to a repo is very different from push, merge or deploy rights. Grant write access only to the repos the job needs.

2 Grok bots · showing 1–2

Editor's picks first, then the most complete listings. Never paid.

Cards Table

  • X Virality Score

    @thegreatest_svCreative

    Creator/blogger desk: watches YOUR watchlist, finds posts that already hit, mines keywords, drafts EN posts to ride the meta, and on first run scaffolds YOUR own public GitHub Pages…

    • Connects to: GitHub, X
    • Asks first
    • Likely scheduled· usage every run
    • Checked 5 Nov

  • Quarto Blog Shipper

    @JavierOrracaCreative

    Ships your Quarto blog through pull requests: drafts posts in your voice, keeps them hidden until you approve, and publishes with GitHub Actions to Netlify, GitHub Pages, or Cloudfla…

    • Connects to: GitHub
    • Asks first
    • On demand· usage when run
    • Checked 5 Nov

What GitHub access allows

Checked against xAI's docs

How it connects. Through the GitHub app in Connect apps. GitHub events (a new issue, a pull request) can also start a routine through a Cursor account integration, which may need its own connection.

It can read

Read risk: Low
  • Repositories, issues and pull requests the connected account can see

It can write

Write risk: High
  • Whatever the connected account and the access you grant allow; xAI's docs we read don't list the GitHub app's individual tools

A Bot with push or merge rights can change production code. Templates that run commands or install packages bring outside code onto the Bot's computer, where your other Bots can reach it.

Set up GitHub safely

  • Grant access only to the repositories the job needs, if GitHub offers you that choice.
  • Prefer review bots that comment or report, and open pull requests rather than pushing.
  • Use a test repository for the first run of any template that writes code.
  • Keep secrets in the secure secret card, never in chat or in a repository.

Ask first rules to add before connecting

In Settings → General → Bot → Custom Rules, describe the action and choose Ask first.

Ask first before pushing, merging, closing or commenting publicly on GitHub.
GitHub templates that say they ask first

GitHub templates that say they ask first

Real listings that name this connector and, in their creators' words, ask before acting. We haven't tested their instructions.

  • PR Babysitter

    @DoonerDesigns_Engineering

    Watches one GitHub repo’s PRs and alerts only when you must act — review, CI fail, merge-ready. Quiet otherwise. Never merges or comments without your yes.

    • Connects to: GitHub
    • Asks first
    • On demand· usage when run
    • Checked 5 Nov

  • Dependency & Secret Audit

    @teeRex247Engineering

    Paste a GitHub repo, get a ranked fix list in 2 minutes: vulnerable packages with exact upgrade commands, leaked keys masked with rotate steps. Read-only; nightly alerts only on new…

    • Connects to: GitHub
    • Asks first
    • On demand· usage when run
    • Checked 5 Nov

  • Connector Scope Check

    @usgworldEngineering

    Before connecting Gmail, Drive, Stripe, GitHub, or calendar to a Grok Bot (or right after Adding a marketplace template), run a minimum-scope checklist and return CLEAR or NEEDS ACTI…

    • Connects to: Email, Calendar +1
    • Asks first
    • On demand· usage when run
    • Checked 5 Nov

GitHub questions

Can a GitHub event start a Grok Bot routine?

Yes. A routine can start on a GitHub event as well as on a schedule. Cursor account integrations start these routines, and they're separate from the GitHub app, so they may need their own connection. Only new activity counts: events from before the trigger existed don't start a run.

Source: Skills and routines

Sources

Checked

What each connection can do comes from these pages. Template counts are listings whose own text or tags name GitHub, a reading aid rather than a verified integration.

  1. Use the computer and apps (opens in a new tab)xAI · first-partychecked 5 Nov 2026The shared computer, connecting apps, what Gmail, Google Calendar, Drive, Sheets, Slack and X can do, MCP servers, the Bot's own email address, public X search.
  2. Skills and routines (opens in a new tab)xAI · first-partychecked 5 Nov 2026Saving a skill, Teach a task, private skills, routines on a schedule or an event, Test, limits (50 routines per Bot, 5-minute minimum, hourly run caps), routines and usage.
  3. Approvals, security, and privacy (opens in a new tab)xAI · first-partychecked 5 Nov 2026Auto Review, approval cards, Ask first rules, approvals expiring after 30 minutes, keeping secrets out of chat, saved cards, local-computer access, least privilege.