← Back to library

Let engineer bots babysit cloud-agent PRs every 30 minutes

Lingxi Li on the Grok Bot team runs five engineer bots, each owning a product area. They track pull requests in a shared Notion database and every half hour look for review or security flags, red builds and conflicting branches, sending cloud agents back to fix issues. Clean ones get a review run; only confident, low-risk changes merge automatically.

  • OutcomeKeep many agent-written pull requests moving overnight: bots check CI, conflicts and review findings, push fixes and queue the good ones for you.
  • SetupAn afternoon+
  • LevelAdvanced
  • CreditLingxi Li
View original
Works with
Grok Bot

Published Oct 23, 2026Updated Oct 23, 2026AI dry run on sample input: passed Oct 23, 2026Source verified Oct 23, 2026

When should you use it?

  • You run many cloud coding agents at once
  • PRs stall on CI failures or conflicts
  • You want a scannable status view

Not for: Teams without automated review; Repositories where every merge must be human-approved

What do you need, and what do you get?

You need

  • Cloud coding agents
  • A shared tracking database
  • CI and automated review tools

You get

  • A status board of PRs
  • Automatic follow-ups to fix problems
  • A ready-for-review queue each morning

How does it work, step by step?

  1. Assign areasGive each bot ownership of one part of the product.
  2. Track work outside chatKeep every PR in a shared database so progress survives context limits.
  3. Check on a timerEvery half hour, look for review findings, failing CI and conflicts.
  4. Send work backAsk the cloud agent to fix problems and set its status back to in progress.
  5. Gate mergingAuto-merge only high-confidence, small-blast-radius changes; queue the rest for you.

The prompt

Our own prompt, inspired by Lingxi Li and written to work in Grok Bot. Values in lime are placeholders.

Prompt0 variables
Every 30 minutes, go through the PR tracker in [database]. For each open PR, check review and security comments, CI status and merge conflicts. Verify each finding is real. If something fails, ask the cloud agent to fix it and set status to Working. If clean, run a code review and set Ready for Review with a summary and test proof. Never merge unless the change matches [low-risk rule].

Inspired by Lingxi Li: Grok Bot for Engineering · Grok Bot. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.

What can go wrong?

  • Auto-merge is risky; define low blast radius narrowly.
  • Review bots raise false alarms; have bots verify each finding.

Our take

Lingxi Li's account from the Grok Bot team comes with the usual caveat that vendor teams describe their own tools, but the shared Notion database is a genuinely good idea: it moves pull-request state out of chat and gives you a board you can scan in seconds. Engineer bots that own a product area and, every half hour, chase review flags, red builds and conflicting branches keep cloud agents from stalling unread. Start with no automatic merges at all. Allow them later only for a narrow class such as dependency bumps, once checks and review bots have earned trust. Require proof of testing attached to every pull request, not just a claim that tests passed. Keep security findings as hard blockers that always need a person. Watch for thrashing, where bots and cloud agents bounce the same failing change back and forth; a limit on retries per pull request stops that. Humans still decide architecture and anything that touches production data or user-facing copy.

Where the time goes back: The constant checking of CI, conflicts and review comments is delegated, so the human only reviews finished work.

FAQ

How many agents can this handle?
The author says she went from about 15 cloud agents by hand to over 200.
What is the urgent mode?
Marking a task P0 starts a routine that checks the agent's transcript every five minutes and steers it.

Source and credit

Inspired by Lingxi Li. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.

Inspired by
Grok Bot for Engineering · Grok Bot
Creator
Lingxi Li
Published on
x.ai
Original date
Sep 10, 2026
License
Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
Originally for
Grok Bot
AI dry run
Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails.
Verified
Oct 23, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.

Are you the creator? Claim or correct this page.

More in Operations & Admin

All 203 Operations & Admin playbooks →

Related playbooks

Operations & AdminPrompt✓ AI dry run

Aim the agent at a janky internal app after it maps the UI

Have the agent study a janky internal UI out loud, complete one end-to-end task with a recording, and stop for login walls instead of guessing credentials.

Credit: Carnage (@0xCarnagee)

Under an hour
Operations & AdminPrompt✓ AI dry run

Chain skills with a yes-gate instead of one giant prompt

Assemble a daily pipeline: pick from a source, draft with a writing skill, wait for your yes, then hand to a planning or build skill.

Credit: Matt Palmer (@mattyp)

Under an hour
Operations & AdminPrompt✓ AI dry run

Copy two working bot roles before you invent one

Start from a short list of narrow, already-used agent roles mapped to your week instead of a vague catch-all Assistant.

Credit: Carnage (@0xCarnagee)

Minutes
Operations & AdminWorkflow✓ AI dry run

Give your bot an email address on your domain

Give an always-on bot a mailbox on your own domain through a custom connector, and wake it with a signed webhook when mail arrives.

Credit: u/Jcoulaud on r/GrokBot

Under an hour
Operations & AdminPrompt✓ AI dry run

Run a fast watcher and a slow watcher, and allow silence

Set an hourly narrow-signal watcher and a daily theme summary watcher, both allowed to report nothing instead of inventing updates.

Credit: Matt Palmer (@mattyp)

Under an hour