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 skipuntil.
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.
Review Rust code changes for unsafe correctness, security and robustness, documentation quality, and C-to-Rust porting fidelity. Use this when you want to review Rust changes before merging.
Guidelines for writing Python flow tests (end-to-end behavioral tests). Use this when writing new Python tests in tests/pytests/, and as the review criteria when reviewing changes to them.
AGENTS.md instructions for RediSearch/RediSearch, covering redisearch development guide, proposing features and large changes, build commands, testing and header generation.
Claude Code instructions for RediSearch/RediSearch, a project described as: A query and indexing engine for Redis, providing secondary indexing, full-text search, vector similarity search and aggregations.
Implementation & review guide for suspend/resume (revalidation) on query-engine iterators in src/redisearchrs/rqeiterators/. Use this when adding the Box suspend/resume mechanism to an RQE iterator that currently only implements the legacy revalidate, when modifying an existing suspend/resume implementation, or when…