Engineering
beet avatar

beet

A specialized tool for managing and preparing Bevy-based Rust crate releases, automating documentation verification, multi-target testing, and example validation.

Introduction

Beet is an automation-focused release management assistant tailored for developers building modular applications within the Bevy Engine ecosystem. It simplifies the repetitive and error-prone process of preparing individual crates for release by enforcing strict quality gates. The agent acts as a checklist manager and verification engine, ensuring that crates are properly documented, feature-complete, and robust across different compilation targets like native Rust and wasm32-unknown-unknown. It is designed for software engineers working on complex ECS (Entity Component System) architectures who require consistent documentation and verified integration examples for their libraries.

  • Automated documentation audits to ensure README files are up to date and correctly integrated into lib.rs crate-level docs.

  • Cross-platform build verification using cargo check for native and WebAssembly (wasm32-unknown-unknown) environments.

  • Automated test suite execution with configurable timeouts and output tailing for better log readability.

  • Structural validation of example code, ensuring that all documented usage patterns have corresponding, runnable, and well-commented examples located in the project's example directories.

  • Integration validation for complex dependencies, specifically supporting crates built with beet_core, beet_flow, and other ecosystem-specific tools.

  • The agent is intended to be run sequentially across specific crates in a repository to ensure release readiness status (ranging from experimental to stable).

  • Input: The tool requires identifying specific crate names within the workspace; it then performs filesystem checks, cargo operations, and command-line execution for live testing.

  • Constraints: The agent does not perform the final publishing step (e.g., cargo publish), serving only as a pre-flight checklist. It requires a configured Rust nightly environment and the just task runner for optimal performance.

  • Use cases include validating release candidates, regression testing before crate updates, and ensuring high-quality documentation standards across the Bevy-based application framework.

Repository Stats

Stars
123
Forks
7
Open Issues
16
Language
Rust
Default Branch
main
Sync Status
Idle
Last Synced
May 4, 2026, 12:54 AM
View on GitHub