review-rust-docs
Review the documentation of a Rust crate to ensure it meets our requirements and standards. Use this when you have done changes to Rust code.
Browse reusable Agent Skills, each with a clear purpose and practical guidance.
Review the documentation of a Rust crate to ensure it meets our requirements and standards. Use this when you have done changes to Rust code.
Run C/C++ unit tests to verify correctness. Use this after making changes to C code to verify nothing is broken.
Run a RediSearch end-to-end macro benchmark from tests/benchmarks/*.yml via redisbench-admin. Use this when you want to measure whole-module performance (throughput/latency) against a real redis-server, not micro Rust or C++ benchmarks.
Run end-to-end Python tests after making changes to verify correctness. Use this when you want to verify your changes from an end-to-end perspective, after ensuring the build and Rust tests pass.
Run Rust benchmarks and compare performance with the C implementation. Use this when you work on migrating C code to Rust and want to ensure performance is not regressed.
Run Rust tests after making changes to verify correctness. Use this when you want to verify your changes to Rust code.
Guidelines for writing Rust tests. Use this when you want to write Rust tests.
Guidelines for writing Python flow tests (end-to-end behavioral tests). Use this when writing new Python tests in tests/pytests/.
Write Rust tests to verify correctness of Rust code. Use this when you want to write Rust tests.
Reviews .NET API surface area PRs for design guideline violations. Analyzes api/*.cs file diffs, applies review rules from .NET Framework Design Guidelines and Aspire conventions, and attributes findings to the developer who introduced each API (via git blame). Use this when asked to review API surface area changes.