// 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.
| name | build |
| description | 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. |
Compile the project to verify changes build successfully.
Run this skill after making code changes to verify they compile.
./build.sh
Use this when you modified C code, or when building for the first time.
./build.sh DEBUG=1
Enables debug symbols and additional assertions. Use this when developing or debugging.
cargo build --manifest-path src/redisearch_rs/Cargo.toml
Only use after the C code has been built at least once with ./build.sh.
If you update C code, run ./build.sh again before the Rust-only build.
./build.sh TESTS
Compiles test binaries (C/C++ unit tests) alongside the module. Required before
running individual test binaries directly (e.g., rstest --gtest_filter=...).
If you encounter strange build errors (stale artifacts, CMake cache issues):
./build.sh FORCE
For Rust only:
(cd src/redisearch_rs && cargo clean && cargo build) # subshell keeps clean+build co-located
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.
Run Rust tests after making changes to verify correctness. Use this when you want to verify your changes to Rust code.