rmc-workspace-overview

Audit a Rust workspace for coupling, dead code, and complexity.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you quickly understand the shape, coupling, hygiene, and risk surface of an unfamiliar Rust workspace so you can choose the right next audit step.

Core Features & Use Cases

  • Workspace-wide first-look audit covering crates, item counts, visibility distribution, and dead-public rot.
  • Architectural coupling analysis using crate-edge fan-in/fan-out and cycle checks to surface the workspace’s structure.
  • Safety and state risk scanning by running unsafe-block documentation checks and global mutable-state inventory.
  • Hygiene and duplication detection via type collisions, module shadowing, within-crate duplicates, and semantic/literal overlap clustering.
  • Complexity hotspot spotting by selecting top-coupled files and estimating cyclomatic complexity before deeper dives.

Quick Start

Run the workspace overview audit by pointing it at your workspace path to get a one-page snapshot plus severity-ranked findings.

Frequently Asked Questions about rmc-workspace-overview

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

FAQPage Schema
How do I audit a Rust workspace for crate coupling and dead public rot?

To audit a Rust workspace for crate coupling and dead public rot, run an overview pass that orchestrates discovery tools for statistics, crate edges, and visibility distribution to produce severity-ranked findings.

What is the best way to detect semantic overlaps and hygiene issues in a Rust codebase?

Detecting semantic overlaps and hygiene issues requires indexing the codebase to cluster type collisions, module shadowing, and literal overlaps, using a configurable threshold for sensitivity.

Can I scan for unsafe surface area and global mutability at workspace scope?

You can scan for unsafe surface area and global mutability at workspace scope by executing unsafe-block documentation checks and mutable-state inventory across all crates in one pass.

How do I find complexity hotspots when onboarding to an unfamiliar Rust codebase?

Find complexity hotspots by selecting top-coupled files from crate-edge analysis and estimating cyclomatic complexity, allowing you to target deeper dives before per-crate audits.

Does the workspace audit require running index_codebase before checking for semantic overlaps?

Yes, checking for semantic overlaps requires running build_hypergraph and index_codebase first to establish the graph structure needed before applying the configurable overlap threshold.