QA bot
Acceptance-checklist QA agent that gives pass, fail or blocked verdicts on live deploys
- Platforms
- Web, API
- Listing updated
- today
Similar agents
About QA bot
QA bot is a Grok Bot for developer tools. It is available on Web and API.
The page describes this as a QA agent that works against the live deployment rather than only in a test environment. Its job is to take a product manager's binding cut and turn it into a canonical set of acceptance criteria, then run those checks against production and report a status of PASS, FAIL or BLOCKED.
The listing stresses a separation between engineering and QA: a green CI run is not treated as acceptance, and items marked as blocking cannot be soft-passed. Expected results are meant to stay fixed rather than being edited to match the outcome. Test fixtures live at a path the owner configures, and each run is written to a dated report with a YAML footer.
The page says the agent can be wired to a GitHub merge listener and a deploy host such as Vercel so it verifies the production commit before running its blocking checks. It is aimed at teams that want a release gate with clear ownership between builders and testers.
What it does
- Acceptance pack generation
- Converts a binding product cut into a canonical list of acceptance criteria.
- Blocking versus warning checks
- Separates hard-blocking items from warnings and refuses to soft-pass blockers.
- Live deploy verification
- Runs the checklist against the production deployment rather than only in CI.
- Dated run reports
- Writes each run to a dated markdown report with a YAML footer.
- Merge-triggered gating
- Can be triggered by a GitHub PR-merged listener and confirm the production commit before testing.
Good for
- Gating a release on a fixed acceptance checklist before shipping
- Verifying a live deploy matches the commit that was merged
- Keeping QA sign-off separate from engineering CI results
- Producing dated audit reports for each release check
QA bot FAQ
What statuses does the agent return?
It emits STATUS PASS, FAIL or BLOCKED. BLOCKED is used when there is no binding product cut yet.
Can it invent acceptance criteria if none exist?
No. The page says that without a binding cut it returns BLOCKED and asks the owner for one rather than inventing criteria.
Does a passing CI build count as acceptance?
The page says engineering CI being clean is not the same as an acceptance pass.
What are the best alternatives to QA bot?
The closest alternatives to QA bot are webqa-agent, Virtuoso QA, Attest, Web and agent-orchestrator.
Where this comes from
- Description: written from the project's website.

