// Run full verification before committing or creating a PR. Use this when you want to create a PR.
| name | verify |
| description | Run full verification before committing or creating a PR. Use this when you want to create a PR. |
Run full verification before committing or creating a PR.
Use this skill to run comprehensive checks before finalizing changes.
Determine which code was modified (C, Rust, or both) and run the appropriate checks.
Run the following checks in order:
clang-format --dry-run -Werror <modified .c and .h files>
If it fails, run clang-format -i <files> to fix formatting.
./build.sh
Ensure the full project compiles without warnings promoted to errors.
./build.sh RUN_UNIT_TESTS ENABLE_ASSERT=1
All unit tests must pass. Use /run-c-unit-tests for details on running specific tests.
./build.sh RUN_PYTEST ENABLE_ASSERT=1
Required for changes to command handlers, query execution, indexing pipeline, or RDB serialization.
./build.sh RUN_UNIT_TESTS SAN=address
coord/ code was modified)Changes to the coordinator (src/coord/), distributed hybrid (src/coord/hybrid/), or
the Map-Reduce layer (src/coord/rmr/) must be tested in a clustered environment:
./build.sh RUN_PYTEST ENABLE_ASSERT=1 REDIS_STANDALONE=0 SHARDS=3
This spins up a 3-shard cluster and runs the full test suite against it.
make fmt CHECK=1
If it fails, run make fmt to fix formatting.
make lint
Fix any clippy warnings or errors.
./build.sh
Ensure the full project compiles.
cargo nextest run --manifest-path src/redisearch_rs/Cargo.toml
All Rust tests must pass.
Run all checks from both sections above.
./build.sh RUN_PYTEST ENABLE_ASSERT=1
For minor Rust-only changes (subshell keeps the chain readable — one cwd hop, three commands):
(cd src/redisearch_rs && cargo fmt --check && cargo clippy --all-targets && cargo nextest run)
For minor C-only changes:
./build.sh && ./build.sh RUN_UNIT_TESTS ENABLE_ASSERT=1
Compile the project to verify changes build successfully. Use this to verify your changes build properly together with the complete project and dependencies, and make sure to use it before running end to end tests.
Investigate a RediSearch flaky-test report from a Jira key, CI failure, test id, or local logs. Use this to collect evidence, identify a supported root cause, and propose a real fix; if the evidence is insufficient, say so and ask for the missing data instead of suggesting workaround-only fixes or skip_until.
Fix merge conflicts in a jj change and its ancestors, starting from the oldest conflict. Use this when a jj change or its ancestors have conflicts that need resolving.
Check code quality and formatting before committing changes. Use this to verify your changes meet our coding standards.
Guide for porting a C module to Rust. Use this when starting to port a C module to Rust.
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.