Grok Bots for engineering: reviewing a diff ranked by what breaks in production, turning a vague complaint into a reproduction an engineer can pick up cold, writing the test plan for the cases people skip, writing SQL that runs with its assumptions named, and writing what customers read during an outage.
Diff Code Review Bot
Findings ranked by blast radius
Repro Bug Bot
Reproduces it, writes the report, stops
Query SQL Bot
A query that runs, with the assumption named
Probe QA Bot
The paths a human would miss, as a checklist that can fail
Page Incident Bot
What broke, who was hit, what you are doing
The ranking. Diff orders what it finds by blast radius, from data loss and security down to naming, and every finding carries the concrete input that fails and the fix as code. A general chat returns a flat list where a style note sits next to a race condition.
No, and it is told not to. It comments on an approach only when the approach causes data loss, a security hole, a correctness bug or a failure it cannot recover from.
Query asks for the schema, and where it has to guess it puts the guesses in a comment block at the top. It is read only by default and never runs a write.
The cases that actually break software: boundaries, interruption, concurrency, permissions, ugly text and the second device. It writes the happy path in one line and moves on.