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.
Backport security patches across maintained release branches
Triage fixes and prepare per-branch patch candidates for review
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 happensNew upstream fix arrives
- ThenMap affected release branches
- ResultDraft backport patches for review
An AI bot that takes an upstream security fix and works out where it needs to land. It inspects the patch, compares it against each maintained release branch, flags conflicts or missing dependencies, and drafts a branch-specific backport for a human to check before anything is merged.
Quick answers
What does it do?
Triage fixes and prepare per-branch patch candidates for review. Result: Draft backport patches for review.
What does it need?
Tools: Terminal, Docs, Chat. Advanced: more tools and setup. The prompt includes an approval step.
How do I run it?
When something happens: New upstream fix arrives. Copy the prompt below into a bot in BotBento.
Prompt to start with
BotBentoRecommended
When a new upstream security fix is provided, read the patch and its context, then determine which maintained release branches are affected. For each branch, compare surrounding code, note conflicts or prerequisite changes, and prepare a candidate backport with a short rationale and any test commands worth running. Keep a per-branch status list and surface anything ambiguous as a question. Do not push commits, open or comment on pull requests, merge, close issues, or message maintainers without explicit approval for each action; present drafts and wait.