Repro, the bug report Grok Bot
Bug report Grok Bot template. Turns a vague complaint into a reproduction: the exact steps, the expected and actual result, the environment, and the narrowest case that still fails.
About this engineering Grok Bot template
Repro is the bug report Grok Bot that reproduces the problem before it writes anything. It opens the URL, follows the steps, then narrows: removing one step at a time until it stops failing, so the report is the smallest case that still breaks.
The report is written to be picked up cold: what fails in under twelve words, numbered steps from a state anybody can reach, expected against actual with the exact error text, frequency as a count rather than the word sometimes, the environment, the console error and the failed request, and a marked guess at where it lives. If it does not reproduce, it says so and lists what it tried, which is a real result that saves somebody a day.
Use Repro on every vague report, which is most of them. Diff is the Grok Bot for reviewing the fix once somebody writes it, Probe for the test that keeps it fixed, and Desk for the customer who is still waiting. The report it produces is the artefact: numbered steps, expected against actual, and the narrowest case that still fails, which is often half the debugging done before an engineer opens the file.
Mentioned above: Diff Code Review Bot, Desk Support Bot, Probe QA Bot. Or see every Engineering Grok Bot.
What to ask it
- A customer says checkout froze. Reproduce it and write the report.
- Narrow this bug to the smallest case that still fails.
- Does this reproduce on mobile at 375 wide?
- Write this up as an issue an engineer can pick up cold.
- I cannot reproduce this. Try, and tell me what you did.
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 Repro Bug Bot to Grok Bot in one click, using Grok Bot's own share as template link.
Questions about this Grok Bot
Does it fix the bug?
No, deliberately. It reproduces, narrows and reports, and may name a suspected cause in one line. Somebody who owns that code writes the fix.
What if it cannot reproduce the problem?
It says so and lists exactly what it tried: the browser, the viewport, the account state, the path. A clean negative is a useful result.
Will this Grok Bot guess at steps it did not perform?
Never. Every step in the report is one it actually took in the product, which is what makes the report safe to hand to an engineer without checking it first.
What does the report include?
Title, numbered steps, expected, actual with the exact error text, frequency as a count, environment, console and network evidence, a marked guess at the location, and a severity.
Design templates for your tool
Repro Bug 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
Query, the SQL Grok Bot
A query that runs, with the assumption named
Probe, the QA Grok Bot
The paths a human would miss, as a checklist that can fail
Page, the incident comms Grok Bot
What broke, who was hit, what you are doing
Browse Grok Bot templates