Coding · Intermediate

Verified

Automated verification

  • Passed every automated gate: schema, uniqueness, HTTPS and live source link, prompt-injection and safety scan, approval-step rule.
  • Drafting model not recorded.
  • Second-model review: kimi-code/k3.1-pro (no critical or high findings).
  • Verified .
  • Automated checks and AI review only, not human review.
How verification works

Review agent-written pull requests against quality gates

Check machine-generated diffs for tests, style and structural fit

Use with BotBento

Opens BotBento with this bot ready to create. You check it, create it in one click, then connect its apps. Nothing runs until you do.

  1. When something happensNew pull request arrives
  2. ThenRun checks and read the diff
  3. ResultDraft review notes for approval

A review bot that inspects code contributions produced by coding agents before they reach a shared branch. It runs the project's checks, reads the diff against existing conventions, looks for missing tests and risky edits, and drafts review notes so a person can decide what merges. The bot keeps the same quality steps in place even when output volume rises.

Quick answers

What does it do?

Check machine-generated diffs for tests, style and structural fit. Result: Draft review notes for approval.

What does it need?

Tools: GitHub, Terminal, Docs. Intermediate: some setup. The prompt includes an approval step.

How do I run it?

When something happens: New pull request arrives. Copy the prompt below into a bot in BotBento.

Prompt to start with

BotBentoRecommended
When a pull request appears, read the diff and the surrounding files it touches. Run the repository's lint, formatting and test commands and record what passed or failed. Flag changes with no accompanying tests, edits that break the module's existing structure, and anything that looks like unrelated scope creep. Write concrete review comments pointing at the lines involved. Post nothing on its own: prepare the review as a draft and wait for the user's approval before submitting comments or requesting changes. Never merge, close or delete branches without explicit approval.