Grok Bot reusable skills: a PR review blueprint

cranger @crangerusOriginally posted 2026.10.26

Open original on X

THIS IS PURE F*CKING TREASURE Grok Bot supports reusable skills. This free PR-review blueprint gives your Bots the playbook you keep typing from scratch. The idea: save the review process once, then reference that skill when the next diff lands. Your checklist stops getting buried halfway up an old conversation, and the next review starts with the same rules. You just give Grok Bot this setup: Save a skill called PR Review. Include the inputs, review steps, evidence format and approval boundary. here's the split: → inputs define the repo, base revision and proposed diff → rules explain which contracts and edge cases to inspect → checks define the evidence every finding must include → you stop rebuilding the review instructions for every new task Three lines do the heavy lifting: → when to use it: a proposed code change needs review → what to return: blocking findings with file references and a clear reason → when to stop: a required input is missing or an action needs approval Inputs arrive. Rules guide. Checks verify. Explicit routing is the same move one layer down: known steps follow the saved playbook, and ambiguous cases go back to the Bot that owns the decision. the full tree > PR Review holds the reusable method > inputs Scout identifies the repo, base revision and diff > rules Scout checks contracts, failure paths and edge cases > checks Scout attaches evidence to each proposed finding > Reviewer checks the skill before it is saved or revised > Builder applies the playbook and returns the review paste the tree and this prompt into Grok Bot ↓ "Build my PR Review skill around this tree: 1. Draft one reusable skill with a trigger, required inputs, review steps, output format and approval boundary. 2. Require the repo, base revision and proposed diff. If anything is missing, ask for it before reviewing. 3. Return blocking findings with file references, reasons and evidence. Separate confirmed issues from questions. Use the read-only review roles inputs, rules and checks to inspect the draft and return concise handoffs. 4. Have Reviewer inspect the skill, then show me the complete text. Save it only after I approve. Reference the approved skill for later reviews; ask before changing its rules. Do not edit source files, merge or publish." ↳ https://docs.x.ai/grok-bot/skills-routines-and-automations save it, you'll use this on the next diff.

This post quotes another post: x.com/k1rallik/status/2114726480559112502