Do the work for clients
Grok Bot GitHub PR review workflow
Brief the bot. Ship the code. Let it review the PR.
shared by @B_doong2daddy ↗
How it's set up
Brief Grok Bot, ship code on GitHub, then let it review the PR, they posted. We have the tweet. We did not sit the review. No dollar. No public install. Tag via @Sable_Project.
- 01Brief your Grok Bot on the repo and the change you already made.
- 02Ship the code on GitHub as you already do. You still own the push.
- 03Ask Grok Bot to review the PR. You still read every note.
- 04You still merge. The bot does not merge on day one.
- 05Write hours from your clock. Do not invent a dollar.
Prompt
We cannot write an honest starter prompt from what was published. Use the steps above.
How the money works
A PR review that catches misses before merge can save billable rework. They posted no dollar. First proof is one PR you opened where the bot left a review you still checked — not a review copied from the tweet.
What to try first
This week: brief Grok Bot on one real PR you opened, ask for a review, and check every note before you merge.
Watch out
- Tokens: wide repo dumps can burn the week. Cap the run.
- Time: one checked review beats a review claim you cannot show.
- Claim: Brief Grok Bot, ship code on GitHub, then let it review the PR is what they posted. Not a review we sat. Not a public install.