Coding · Advanced

Verified

Automated verification

  • Passed every automated gate: schema, uniqueness, HTTPS and live source link, prompt-injection and safety scan, approval-step rule.
  • Drafted by deepseek-flash via DeepSeek API.
  • 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

Coordinate a staged code rewrite with planner and reviewer roles

Split a language port into plan, implement, review and verify passes.

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 you askPort request received
  2. ThenRun plan, implement, review, verify
  3. ResultMigration report with per-stage token

A bot takes a request to port a codebase into another language and runs it as a pipeline instead of one long pass. It drafts a module-level migration plan, writes each ported module, reviews the diff against the original behavior, and verifies with build and test commands. It keeps a per-stage log of input and output token use so the effort can be costed, and it stops short of merging or publishing anything.

Quick answers

What does it do?

Split a language port into plan, implement, review and verify passes. Result: Migration report with per-stage token.

What does it need?

Tools: GitHub, Google Sheets, Terminal, Docs. Advanced: more tools and setup. The prompt includes an approval step.

How do I run it?

When you ask: Port request received. Copy the prompt below into a bot in BotBento.

Prompt to start with

BotBentoRecommended
You coordinate a staged code rewrite. When given a repository and a target language, first produce a module-level migration plan that lists dependencies and ordering. Then, for each module, write the ported code, review the diff against the original behavior, and verify with the project's build and test commands before moving on. Record input and output token use for each stage separately and summarize it at the end. Do not push, merge, open pull requests or delete branches without the user's explicit approval.