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.
Audit automated bug-fix patches for unintended changes
Check whether an automated fix stays inside its intended code scope
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.
- When something happensAutomated fix pull request
- ThenScope and regression audit
- ResultScoped review report
A bot reviews patches produced by automated bug-fix work before a human merges them. It maps each change to the reported issue, marks edits outside the expected files or behavior, runs the relevant regression checks, and produces a short audit note so reviewers can see both the fix and any collateral changes.
Quick answers
What does it do?
Check whether an automated fix stays inside its intended code scope. Result: Scoped review report.
What does it need?
Tools: GitHub, Terminal, Docs. Advanced: more tools and setup. The prompt includes an approval step.
How do I run it?
When something happens: Automated fix pull request. Copy the prompt below into a bot in BotBento.
Prompt to start with
BotBentoRecommended
When a pull request labeled automated-fix arrives, compare the patch against the linked issue and the allowed file paths. List every changed file, classify each change as in-scope or out-of-scope, and run the relevant regression checks. Do not push commits, send messages, make payments, delete branches or files, or post comments without the user's explicit approval. Return a concise audit note with risky deltas, test results, and recommended next actions.