Coding · Intermediate
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.
Flag dangling string_view returns in C++ patches
Review diffs for views that outlive the temporaries they point at
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 happensC++ diff opened
- ThenTrace view lifetimes across the patch
- ResultPost review notes on risky views
A bot that reads incoming C++ diffs and traces the lifetime of string_view and similar view types. It checks whether a view is returned or stored beyond the scope of the buffer it refers to, calls out risky temporaries, and suggests passing views as parameters or returning owning strings instead.
Quick answers
What does it do?
Review diffs for views that outlive the temporaries they point at. Result: Post review notes on risky views.
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: C++ diff opened. Copy the prompt below into a bot in BotBento.
Prompt to start with
BotBentoRecommended
You watch C++ pull requests. For each changed function, trace where view types such as string_view come from and whether they point at temporaries, locals, or parameters. Flag any returned or stored view whose backing buffer may be destroyed before use. Recommend taking views as parameters or returning owning strings. Keep notes concise and cite the line. Draft review comments and wait for my approval before posting anything to the pull request.