// Check code quality and formatting before committing changes. Use this to verify your changes meet our coding standards.
| name | lint |
| description | Check code quality and formatting before committing changes. Use this to verify your changes meet our coding standards. |
Check code quality and formatting before committing changes.
Run this skill to check for lint errors and formatting issues.
Check C/C++ formatting against .clang-format:
clang-format --dry-run -Werror <modified .c and .h files>
If formatting check fails, apply formatting:
clang-format -i <modified .c and .h files>
Verify the project compiles without warnings-as-errors:
./build.sh
The CMake build promotes key warnings to errors (-Werror=incompatible-pointer-types,
-Werror=implicit-function-declaration). A successful build confirms these pass.
Run the lint check:
make lint
If clippy reports warnings or errors, fix them before proceeding
Check formatting:
make fmt CHECK=1
If formatting check fails, apply formatting:
make fmt
If license headers are missing, add them:
(cd src/redisearch_rs && cargo license-fix) # subshell: custom subcommand, no --manifest-path
// SAFETY: comment explaining why the unsafe code is sound#[expect(...)]: Prefer over #[allow(...)] for lint suppressionscargo clippy --manifest-path src/redisearch_rs/Cargo.toml --all-targets --all-features
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.
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.