rig-review

Automated code review checks Rust code changes against mandatory quality gates, including WASM compatibility, error handling, and coding style. It analyzes code structure and dependency usage to ensure contributions meet project standards before opening a pull request.

The pre-commit code review checks Rust code for adherence to mandatory coding standards, specifically targeting error handling patterns, WASM compatibility, and documentation quality. It catches common issues like improper String error types and unwrap() usage to prevent wasted review cycles.

Yes, you need to run cargo fmt, cargo clippy, and cargo test to confirm code integrity and correctness for Rust quality gates. Executing these commands validates formatting, identifies linting violations, and verifies that the code changes pass all required tests.

Your Rust code fails pre-PR validation because unwrap() usage violates mandatory error handling patterns and coding style standards. The automated code auditing process catches these common issues, along with missing documentation and String error types, to ensure robust code quality.

Yes, you can use automated code auditing to check missing documentation in Rust projects. The validation process analyzes comment quality and verifies documentation standards, ensuring all code changes adhere to the required project quality gates before submission.