Grok Bots Directory
Submit a Grok Bot

Benny: triage, reproduce, then fix

Benny is a routine for bug reports. Each report moves down a line of triage, repro, and fix, and any stage can stop it.

lauren @poteto

Source: article "Loops You Can Trust" ·

The playbook

The playbook is a line for incoming bug reports. A bot watches the channel where reports land, such as a Slack feedback channel. Triage reads each report with its screenshots and videos, works out which feature it is about, checks the reporter's version, and searches for duplicates. A clear bug gets a ticket and a handoff. Repro then opens a real build in the cloud, follows the reporter's path, and has to hit the exact broken state twice, with screenshots and video. Only then does a fixer write a test when it can, make the smallest fix it can prove, and open a draft PR.

In lauren's words, "every stage can stop the line." Triage can decide the report describes expected behavior. Repro can fail to reproduce it. The fixer can decide the change is too risky. She counts all three as useful outcomes, because they keep bad work from reaching the next stage, where it costs more to correct. The evidence also changes review. The before and after video already shows the fix works, so review time goes to the code itself.

How a Grok Bot runs Benny

  1. Subscribe to the reports

    A Grok Bot routine watches a Slack feedback channel or Sentry alerts. When related reports arrive in a burst, lauren sends them to one project instead of one agent per bug, so the thread between them is not lost.

  2. Triage with one verdict

    Read every attachment, name the feature, check the version, search the tracker for duplicates, and look at recent changes. Post one verdict in the report's own thread. Create a ticket only for a clear, new bug: no ticket beats a guessed or duplicate one.

  3. Reproduce twice, with evidence

    A cloud agent opens a real build and drives the reporter's path with the verification skill and its feature map. The broken state has to appear twice, captured in screenshots and video. If an open PR or commit already covers the bug, it checks that fix before and after instead of writing a new one.

  4. Hold the line for people

    The repro stays open in the thread so people can correct or reject it. A fix starts only if nobody objects and the root cause is clear. No confirmed repro means no fix.

  5. Fix small, open a draft

    Write a failing test when it can, make the smallest fix it can prove, and run the same path before and after. Then open a draft PR with the repro steps and evidence. Benny never merges or deploys.

Inspired templates2

A template is listed here only when its own skills, memory, or profile take incoming bug reports, work out what they describe, and reproduce them with evidence for whoever fixes them. Ticket routers, support inboxes, and QA bots that test without a report to start from are not listed.

All templates with pstack

Bug Repro Desk

Bug Repro Desk

by Gordan

Turns a ticket or screenshot into a staging repro pack another engineer can follow: exact steps, expected vs actual, environment, and evidence. Never productio…

  • Memories0
  • Skills4
  • Routines0
Bug Reproduction

Bug Reproduction

by SpaceX

Give engineers reports they can trust. Catches the thread, clicks the same path in staging, captures the failure, and drops a repro pack (steps, screenshots, n…

  • Memories0
  • Skills0
  • Routines0

More playbooks

All playbooks