Bee Reviewer 🐝
Bee Reviewer is a Python CLI tool that generates narrated, interactive code reviews. It uses a "Context-Aware" architecture where your AI agent (Claude, Gemini, etc.) directly generates review recipes as it works, ensuring the narration captures the full intent and design decisions of every task.
🌟 Features
- Context-Aware: Review recipes are generated inside the AI session, capturing planning and reasoning that raw git diffs often miss.
- Narrated Presentation: A cinematic web-based slideshow where your code is explained via high-quality text-to-speech.
- Turnkey Viewer: A self-contained web viewer with syntax highlighting, auto-play narration, and full playback controls.
- Cross-Agent Support: Works with Gemini CLI, Claude Code, Aider, and any other AI agent via
BEE-REVIEWER.md. - Zero Token Overhead: No secondary AI calls required for reviews.
🚀 Installation
Install via pip:
pip install bee-reviewer
🛠️ Getting Started
1. Initialize your project
Run this command in the root of your project:
bee-reviewer init
This will:
- Print the Bee Reviewer banner.
- Create a
.bee-review/directory to store your reviews. - Detect your agent (
CLAUDE.md,GEMINI.md) or create a fallbackBEE-REVIEWER.md. - Inject instructions telling the AI to generate a
recipe.jsonin.bee-review/after every completed task.
2. Work with your AI Agent
Continue working with your AI agent as usual. After every human prompt you provide, the agent will silently create a new review file in the .bee-review/ folder.
3. Launch a Review
When you're ready to watch your progress:
bee-reviewer review
- Select a review from the chronological menu.
- A local web server starts, and your browser opens to a narrated slideshow of your changes!
📖 Manual Usage & Advanced Tips
Custom Agent Launch
You can initialize and immediately launch your AI agent in one command:
bee-reviewer init --launch gemini
💡 Pro Tips for Better Reviews
- Baseline Commits: For the best review experience, run
git commit -m "baseline"before starting a major task. This gives the AI a clean reference point for its narration. - Large File Handling: The AI instructions include a 1,000-line limit per file. If a file is larger, the AI is instructed to include only the most relevant 1,000 lines to keep your sessions fast and lightweight.
- Recipe Management: All review recipes are stored as JSON files in the
.bee-review/directory. You can safely delete old files you no longer need, or share specific.jsonfiles with teammates. - Shell Completion:
bee-reviewersupports tab-completion. To enable it for your shell, run:bee-reviewer --install-completion
🛑 Stopping the Server
Press Ctrl+C in your terminal to stop the review server. This safely returns you to your shell.
📄 License
MIT
Metadata
Release files for bee-reviewer 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| bee_reviewer-0.1.0.tar.gz | 11.7 kB | Without provenance | Details for bee_reviewer-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| bee_reviewer-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for bee_reviewer-0.1.0-py3-none-any.whl |
Total release size: 23.2 kB
Release files / bee_reviewer-0.1.0.tar.gz
| Download URL | bee_reviewer-0.1.0.tar.gz |
|---|---|
| Size | 11.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
95724913d031ce3d04fb1ec797e5551932166946c569d7c80552d58f6ef1b299
|
|
BLAKE2b-256 checksum How to use checksums |
6b428c775053bc2c034c1262733da50e99c4d97520d88133820dbc74ad460a85
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.0
|
Release files / bee_reviewer-0.1.0-py3-none-any.whl
| Download URL | bee_reviewer-0.1.0-py3-none-any.whl |
|---|---|
| Size | 11.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
31c5ed05a2e390dc1fd61b8675829e4617202cf987fda0071380b2603d20c73e
|
|
BLAKE2b-256 checksum How to use checksums |
e737d1978a37c352dcc015b107f055267c9117e0e4a71a43a3997731e64dca28
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.0
|
Security for bee-reviewer 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.