read-unmodified-c-module
Read the source of the C module we are working on, before we made any changes.
Browse reusable Agent Skills, each with a clear purpose and practical guidance.
Read the source of the C module we are working on, before we made any changes.
Report a flaky RediSearch test from a CI failure, Jira issue, test id, or local log. Use this to collect GitHub Actions logs/artifacts, find or create the right MOD Jira ticket, update existing flaky-test issues, and suggest immediate triage such as a trivial test-only fix or a temporary skip_until.
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 documentation. Use this when you want to write Rust documentation.
Guidelines for writing Rust tests. Use this when you want to write Rust tests.