Audit Rust module imports, exports, and re-exports for visibility discipline.
npx skills add https://github.com/molaco/rust-code-mcp --skill rmc-module-audit
Please help me install this Agent Skill. Skill: rmc-module-audit Source: https://github.com/molaco/rust-code-mcp/tree/main/skills/rmc-module-audit Command: npx skills add https://github.com/molaco/rust-code-mcp --skill rmc-module-audit
This Skill helps you assess whether a specific Rust module’s internal structure, imports, re-exports, and consumer-visible APIs are consistent, intentional, and visibility-disciplined.
pub items against get_exports for an external consumer, highlighting pub(crate) leaks.rmc-symbol-forensics or crate-root API surface checks to rmc-api-surface.Ask the Skill to audit the module my_crate::foo::bar for consumer crate my_client_crate after you have built the hypergraph for your workspace.
High-intent search queries and answers about installing and using this skill.
To audit Rust module API hygiene, you need to traverse the module tree and compare declared re-exports against consumer-filtered exports to detect unintended exposure and dead facades. This validates whether the module's internal structure and visibility discipline are intentional.
A dead facade in Rust module exports occurs when declared re-exports do not align with consumer-visible APIs. You detect dead facades by running module and file dependency queries, then comparing declared versus consumer-filtered re-exports to highlight visibility mismatches.
To check for pub(crate) leaks in a Rust module, compare the module-tree pub items against the get_exports results for an external consumer. This export and visibility mismatch detection highlights where internal visibility restrictions unintentionally leak into the public API.
Inspect Rust module imports and file-level dependencies by running module-by-module dependency queries during code review. This identifies what the module pulls in and where file-level dependencies matter, ensuring submodule boundaries remain consistent and intentional.
Yes, Rust module visibility checks produce severity-ranked findings classified as high, medium, low, or info. These decision-focused results classify export and re-export mismatches to enable faster triage during module-level code review.
After auditing Rust module exports, you should hand off deeper per-symbol work to specialized symbol forensics tools, or route crate-root API surface checks to dedicated API surface analysis tools for broader visibility validation.
molacoEnforce declarative Rust crate-edge dependency rules and return structured violation JSON.
JylhisExtract and categorize Rust workspace symbols into hierarchical views.
tylerburleighQuery machine-readable codebase documentation for classes, functions, modules, and dependencies.
molacoAudit a Rust crate's public API for accidental exposure and dead items.