rmc-imports-exports

Audit Rust workspace import/export structure for dead public APIs and coupling hotspots.

29|5|Updated Nov 24, 2025
One-click install
npx skills add https://github.com/molaco/rust-code-mcp --skill rmc-imports-exports
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rmc-imports-exports
Source: https://github.com/molaco/rust-code-mcp/tree/main/skills/rmc-imports-exports
Command: npx skills add https://github.com/molaco/rust-code-mcp --skill rmc-imports-exports

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you identify whether a Rust workspace’s cross-crate API boundaries are clean and intentional by finding which crates export what, which consumers actually use it, and where declared public surface is dead or misleading.

Core Features & Use Cases

  • Workspace-wide import/export audit: Builds a consumer→producer edge matrix, then cross-checks declared pub use re-exports against dead-public findings to classify live facades vs dead facades vs dead canonical pubs.
  • Single-crate deep dive: Maps a crate’s root-level module visibility, declared re-exports, imports, and cross-crate dead-pub items to assess encapsulation discipline and API hygiene.
  • Hot-symbol forensics: Uses symbol-level usage summaries to determine whether dependencies are pulled broadly or heavily, and to support targeted refactoring decisions.
  • Optional architecture metrics: Provides Martin-style dependency instability and abstractness metrics to help prioritize architectural cleanup.

Quick Start

Run rmc-imports-exports on your Rust workspace directory to generate a severity-ranked report of dead and over-broad cross-crate import/export surfaces.

Frequently Asked Questions about rmc-imports-exports

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find dead public APIs across Rust workspace crates?

Auditing Rust crate boundaries detects dead public APIs by building a consumer-to-producer edge matrix and cross-checking declared `pub use` re-exports against actual usage, classifying surfaces into live facades, dead facades, or dead canonical pubs.

What is a misleading re-export facade in a Rust crate architecture?

A misleading re-export facade in Rust is a declared `pub use` statement exposing a public API surface that no workspace consumers actually import, creating dead structural coupling classified during a cross-crate boundary audit.

How do I check Rust crate dependency coupling and instability metrics?

Check Rust crate dependency coupling by generating symbol-level usage summaries to measure dependency pull breadth, optionally supplemented by Martin-style dependency instability and abstractness metrics to prioritize architectural cleanup.

Can I audit a single Rust crate's module visibility and encapsulation?

Yes, single-crate deep dives map root-level module visibility, declared re-exports, imports, and cross-crate dead-pub items to assess Rust API encapsulation discipline and hygiene for refactoring or onboarding.

What is the best way to analyze Rust workspace boundaries after a merge?

The best way to analyze Rust workspace boundaries post-merge is running a workspace-wide import/export audit that generates a severity-ranked report of dead and over-broad cross-crate API surfaces for post-merge hygiene.