Run your software releases and testing with Slack bots
A developer set up two Grok Slack bots that notify contributors, run builds, send 10+ agents to test like users, and hand bugs to a fixing bot.
Done with OtherGrok 4.7
What they did
A developer made two team bots with Grok Bot in a dedicated Slack channel. When told to start a release, the release bot messages each contributor about their changes so they can raise blockers. It runs the build and launches 10+ testing agents, some following a feature map and some clicking randomly. Found bugs go to an engineer bot that fixes them in Cursor.
How it went
The author says the whole release and testing process is now handled by the bots. He decides by severity whether a fix ships as a patch or waits for the next release.
Worth knowing
Mixing directed testers with a few random-clicking 'chaos' agents helps catch problems scripted tests miss.
Try it yourself
When I say 'start release' in [Slack channel], list all changes merged since the last release of [repo URL] and message each contributor with links to their changes, asking for blockers. Then start the build and monitor it. Once it passes, test the build like a real user, following [feature list], plus some random exploring. Report each problem with steps to reproduce and severity. Draft fixes for high-priority issues but wait for my approval before merging or publishing any release.
Swap the highlighted [parts] for your own details.
Source: X · @irongiantXBT · Oct 18, 2026
Written with AI assistance from the original post and checked against our editorial guidelines. Results are as reported by the source, not independently verified. Spotted a mistake? Tell us.
