Grok Bot Profiles

Grok Bot Profiles is an open-source collection by HAEGONG of ready-to-use profiles for Grok Bots. Each profile gives a bot one focused job, a concrete deliverable, and an explicit point where its authority ends. The repository currently includes four development profiles: Spec Writer, Bug Reproducer, PR Producer, and PR Verifier.

What It Is

The repository is a library of bot profiles meant to keep responsibilities separate instead of using one general-purpose agent. Specification, investigation, implementation, and verification are handled by different bots, so a bot never approves its own work. Each bot directory contains a PROFILE.md (identity, job, output contract, working rules, approval boundary), a SETUP.md (one-time setup message and operating checklist), and a README.md (installation, required integrations, related bots, first task).

Setup path

Grok Bot does not import local files, so installation works through a URL. You create a new Grok Bot, paste the raw SETUP.md URL of the chosen profile as the first message, connect GitHub when asked, and then send the first task from the profile's README. SETUP.md fetches the profile and configures the bot's Name, Title, and Description. The YAML frontmatter in PROFILE.md maps to the app's Name, Title, and Plugins, while the avatar is configured directly in the app. The repository also provides CREATE_YOUR_OWN_BOT.md with a template, an AI-assisted creation prompt, and a review checklist.

How the development workflow is split

Spec Writer turns a selected idea or unclear issue into an implementation-ready specification. Bug Reproducer turns a bug report into a reproducibility verdict and evidence report. PR Producer turns approved work into a focused branch and reviewable pull request. PR Verifier independently evaluates a pull request and returns PASS, BLOCK, or HOLD. The first three roles can share a production group chat, while PR Verifier works in its own conversation. Handing a draft to another bot is not approval: PR Producer implements only a version you approve, and a human makes the final merge decision.

Boundaries by design

Each bot has a defined stopping point: Spec Writer stops before approving or implementing the spec, Bug Reproducer before editing code, PR Producer before implementing without approval or merging, and PR Verifier before implementing fixes or merging. The README notes that bots share one computer and browser session per account, so the separation protects the basis for a verdict rather than acting as a security boundary. The content is licensed under CC BY 4.0.