Probe, the QA Grok Bot
QA Grok Bot template. Writes the test plan for the cases people skip: the boundaries, the interruptions, the second device, the slow network. Every check has a pass and a fail.
About this engineering Grok Bot template
Probe is the QA Grok Bot that writes the happy path in one line and then spends the whole plan on where software actually breaks. Boundaries, ugly text, numbers, time, interruption, concurrency, permissions, state and environment.
The list is specific because the failures are. Zero, one, the maximum and the maximum plus one. An apostrophe in a surname, an emoji, right to left script, HTML in a text field. Midnight, the end of a month, a daylight saving change, two users in different time zones. Closing the tab mid action, double clicking the button, losing the network halfway. The same record edited in two tabs. A revoked invite, an expired session mid action. Every check states what passing looks like and what failing looks like, because a check that cannot fail is not a check.
Use Probe before a release, and on anything touching money, permissions or data. Diff is the Grok Bot for the review, Repro for turning a found bug into a report, and Page for what customers read when one gets through. Probe caps the plan at what can actually be run in the time available and says what it left out, because a hundred item plan that nobody finishes tests nothing.
Mentioned above: Diff Code Review Bot, Repro Bug Bot, Page Incident Bot. Or see every Engineering Grok Bot.
What to ask it
- Write the test plan for this checkout change.
- What breaks if two people edit the same record in two tabs?
- Give me the boundary cases for this limit.
- Which of these are worth automating and which need one human pass?
- What three things might break elsewhere because of this change?
How to install this Grok Bot template
- Copy the template. You get the name, the description and the instructions.
- In Grok Bot, choose New, then Create new agent.
- Open Bot actions, then Edit Profile, and paste the name and the description.
- Paste the instructions.
- Switch on Web browsing. It needs no routines.
Or skip all five: add Probe QA Bot to Grok Bot in one click, using Grok Bot's own share as template link.
Questions about this Grok Bot
Does this QA Grok Bot cover the happy path?
In one line. It is already covered by everybody who touched the feature, and the value of a plan is in the cases nobody thought about.
How is the plan ordered?
By what a failure would cost: data loss, then money, then a blocked main path, then annoyance. It caps the plan at what can actually be run and says what it left out.
What makes a good check?
One that can fail. Every line has a setup, an action, what passing looks like and what failing looks like, never verify it works correctly.
Does it flag regression risk?
Yes, the three things most likely to break somewhere else because of the change, and how to check each.
Design templates for your tool
Probe QA Bot works alongside the vibe coding tool you already build in, and the same licence covers the design templates for it: Lovable templates, Bolt templates, Replit templates, Claude Code templates, ChatGPT Codex templates, Cursor templates, Windsurf templates, Framer templates, v0 templates and Cline templates.
Included in the BrowserMoon licence, alongside every design template and all 51 Grok Bot templates. One licence, unlimited projects, including work you sell.
More Engineering Grok Bot templates
View allDiff, the code review Grok Bot
Findings ranked by blast radius
Repro, the bug report Grok Bot
Reproduces it, writes the report, stops
Query, the SQL Grok Bot
A query that runs, with the assumption named
Page, the incident comms Grok Bot
What broke, who was hit, what you are doing
Browse Grok Bot templates