Analyze Rust Ffi Crate Surface

What it does

This skill analyzes Rust Foreign Function Interface (FFI) crates or files to identify C-visible symbols and determine their usage within a C codebase. It compiles a list of these symbols, such as functions annotated with #[unsafe(no_mangle)] or type definitions, and then identifies which modules in the C code utilize them. The skill leverages auto-generated header files for assistance when available.

When to use it

• When integrating Rust code into existing C/C++ projects via FFI.
• To understand how specific Rust functions or types are being used within a larger C codebase.
• During refactoring or maintenance of systems that combine Rust and C components.
• To verify the correctness of generated header files for FFI interfaces.

Key capabilities

• Identifies C-visible symbols (functions, types) in Rust FFI crates/files.
• Determines which modules in a C codebase use those symbols.
• Generates reports detailing symbol name, usage module(s), and type.
• Distinguishes between symbols used in production code versus unit tests.
• Utilizes auto-generated header files (located in src/redisearch_rs/headers) for analysis.

Example prompts

• "Analyze the numeric_range_tree_ffi crate to identify all exposed FFI symbols and their usage."
• "What C modules use the function defined in src/redisearch_rs/c_entrypoint/some_file.rs?"
• "Generate a report for the src/redisearch_rs/another_file.rs file, listing all FFI symbols and their usage locations."

Tips & gotchas

• Paths to Rust files should typically start with src/. If not, the skill assumes they are located within the src/redisearch_rs/c_entrypoint directory.
• If a directory is provided as input, the skill will review all Rust files within that directory.
• Auto-generated header files in src/redisearch_rs/headers can be helpful resources during analysis.