RediSearch
@RediSearch Organization
Public Skills
run-python-tests
by RediSearch
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.
analyze-rust-ffi-crate-surface
by RediSearch
Determine which parts of the C codebase use Rust-defined C symbols. Use this when you want to understand which C code files may be impacted by changes to a Rust FFI crate.
write-rust-tests
by RediSearch
Write Rust tests to verify correctness of Rust code. Use this when you want to write Rust tests.
lint
by RediSearch
Check code quality and formatting before committing changes. Use this to verify your changes meet our coding standards.
rust-tests-guidelines
by RediSearch
Guidelines for writing Rust tests. Use this when you want to write Rust tests.
build
by RediSearch
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.
check-rust-coverage
by RediSearch
Check which Rust lines are not covered by Rust tests. Use this when you developed new Rust code and want to ensure it is tested.
port-c-module
by RediSearch
Guide for porting a C module to Rust. Use this when starting to port a C module to Rust.
review-rust-docs
by RediSearch
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.
jj-split-changeset
by RediSearch
Split a jj (Jujutsu) changeset into smaller, focused changesets. Use when asked to break up a large changeset, split commits, reorganize changes across revisions, or create stacked PRs from a single changeset. Covers safe duplication-based workflows, file-path and hunk-level splitting without interactive commands.
read-unmodified-c-module
by RediSearch
Read the source of the C module we are working on, before we made any changes.