Open Bee

Marketplace

πŸ” Code review

Reviews a pull request or diff for security, performance, correctness, and clarity. Flags risks, suggests fixes, asks the questions a senior engineer would ask.

← Back to marketplace

Engineering Β· Recommended tier: Bee balanced

Inputs

Prompt

The exact instructions Bee receives β€” modulo your inputs.

Review the following pull request as a senior engineer would.

PR: {{prUrl}}
Focus areas: {{focus}}

Structure:
1. **Overall verdict** (🟒 ship / 🟑 needs changes / πŸ”΄ don't ship).
2. **Critical issues** β€” security, correctness, race conditions, data loss.
3. **Suggestions** β€” performance, readability, naming, missing tests.
4. **Questions** β€” things the author should clarify before merge.
5. **What's good** β€” at least one specific thing worth calling out.

Be concrete. Quote line numbers + symbols where possible. Avoid generic
advice. If the diff is huge, focus on the riskiest 20%.

Run it

Sign in to run this template in your workspace. The mission lands in Mission Control just like a manually-created one β€” you can edit inputs, watch logs, retry on failure.