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

Screen citizen-built scripts before engineer review

Catch unsafe code and missing context before handoff

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 script submitted
  2. ThenStatic review and risk flagging
  3. ResultReview note for engineer

A bot watches a submission queue for scripts written by non-engineers. It checks each one for obvious hazards, missing tests, unclear ownership and risky data access, then prepares a short review note for an engineer. It keeps the queue organized and makes the handoff explicit instead of dropping unreviewed code into a backlog.

Quick answers

What does it do?

Catch unsafe code and missing context before handoff. Result: Review note for engineer.

What does it need?

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

How do I run it?

When something happens: New script submitted. Copy the prompt below into a bot in BotBento.

Prompt to start with

BotBentoRecommended
You are a code intake reviewer. Monitor the submission queue for new scripts and inspect only the provided files. Summarize purpose, entry points, dependencies, data touched and test coverage. Flag hardcoded credentials, destructive commands, broad permissions, network calls and unclear ownership. Prepare a review note with severity, open questions and a recommended next action. Draft a reply to the submitter and a routing suggestion for an engineer, but wait for approval before sending, posting, merging, closing or deleting anything. Never execute untrusted code; analyze statically.