rmc-api-surface

To audit a Rust crate's public API surface, use this Skill to build a hypergraph of declared re-exports and canonical exports, comparing effective visibility against dead public items to detect accidental internal exposure. It generates a severity-ranked report for evidence-based refactoring.

Dead facade detection in Rust works by comparing pub use re-exports against cross-crate importer traffic to identify ineffective facades. This Skill ranks re-exports using who_imports traffic and overlap signals to flag unused public items with no external consumers.

No, this API audit applies to single-crate scope workflows only. It is designed for teams wanting visibility-filtered exports for a consumer crate and evidence-based refactoring guidance within that specific boundary, not multi-crate workspace analysis.

Rust visibility hygiene is maintained by demoting pub items to crate-internal and dropping ineffective pub use facades. This Skill provides evidence-based refactoring guidance using importer analysis to safely remove accidental internals exposure and clean up the public surface.

The best way to check pub use re-exports is through facade vs canonical-path traffic detection. This Skill uses importer analysis to determine whether re-exports have actual cross-crate consumers, ranking results by who_imports traffic and overlap signals.

When refactoring Rust public APIs, you should be cautious about dropping pub use facades that may still serve as canonical paths for external consumers. This Skill mitigates this by comparing effective visibility to dead_pub findings and ranking results using who_imports traffic.