Engineering
Self-check before merge: bot QA so you are not the only gate
Your bot opened a PR and you are still the only QA.
What hurt
NiNE (@AfterThe925) steals a Monday checklist point from poteto (Grok Bot eng lead) via Peter Yang: give bots a way to check their own work. Lauren's bots test each change before merge — sometimes she does not even look at the PR until after it lands. Concrete steal: add one self-check step to the skill (run tests / lint / your desk gate) and block merge until it passes. Tip only. Not affiliated with xAI.
What to install or create
Skill + self-check (tests/lint/desk gate) → block merge until green → human optional until after land.
Bots
PR self-check bot
After coding, run tests/lint/desk gate and refuse merge until checks pass.
Plugins
GitHub
Required
Files
Skill clause: self-check step + merge blocked until green.
Routines
None on the first run. Watch one manual pass first.
The prompt
This is a tip, not a pasteable system prompt. The author did not publish one. Follow the first-run steps.
First run
- 1Read https://x.com/AfterThe925/status/2104706382272311683 (credit poteto via Peter Yang).
- 2Open the skill your coding bot uses before it opens or merges a PR.
- 3Add one mandatory self-check: run tests, lint, or your desk gate — same bar you would run by hand.
- 4Block merge (or mark the PR not-ready) until that check is green.
- 5Keep production deploy on a human approval if you want a second wall.
Approval fence
Production deploy can stay human-gated even if merge is bot-tested.
What to tweak
Steal one mandatory self-check in the skill. Stop being the only QA on bot PRs.
Source
NiNE @AfterThe925 · Original post
Not affiliated with xAI. We did not write this prompt. Third-party template terms still apply.
Pro pack
PR & deploy watcher: reviews, deploy checks, error triage
Wakes on GitHub, deploy and error events. It reviews each PR, checks the live site after deploys and triages error spikes, and hands small fixes to a cloud coding agent. Nothing merges or deploys without you.