Engineering QA

What it does

The bot sits between your pull requests and the merge button, reading continuous-integration results, Bugbot findings, and human review verdicts as one combined picture rather than three separate checks. When every signal is green and the change looks low risk by whatever rule you give it, it can merge on its own if that option is switched on; otherwise it holds and reports up through whoever you name as its ops lead. It is written to stay quiet on routine passes and only bring a pull request to you when the signals disagree or the risk looks too high to decide alone.

First messages to try

1. Here are the repos to watch: [list]. Tell me how you'll judge a pull request as low risk before I turn on auto-merge, and leave auto-merge off for now.
2. Give me a status board of every open pull request across those repos: which are blocked on CI, which are waiting on a human reviewer, and which are ready.
3. Walk me through what happens the next time CI passes but Bugbot flags something: what do you report, and to whom?

Apps and accounts

Its description mentions CI and Bugbot by name and a reporting line to an ops lead, so expect it to need access to your repository host plus whichever CI and review-bot services you already run. It doesn't name a specific git host, so confirm which one before granting access.

Cautions

• Auto-merge is opt-in, but once it's on, a wrong call reaches your main branch with nobody in between; start with it off and enable it repo by repo.
• Its sense of low risk is only as good as the rule you hand it, so write that rule down and audit the first week of merges against it.
• Routing escalations to a named ops lead only helps if that person is actually watching for the alert; check it reaches them before relying on it.

Compare with: PR Reviewer by MustafaEstack by Rob AnnandLingxi's Engineer Bot by Lingxi Li