Identify used and dead methods in a Rust type's public API.
npx skills add https://github.com/molaco/rust-code-mcp --skill rmc-method-api
Please help me install this Agent Skill. Skill: rmc-method-api Source: https://github.com/molaco/rust-code-mcp/tree/main/skills/rmc-method-api Command: npx skills add https://github.com/molaco/rust-code-mcp --skill rmc-method-api
This skill helps you identify which methods on a specific Rust type are actually used in the codebase, including dead APIs, test-only helpers, and naming inconsistencies.
who_uses_summary, enabling you to rank critical entry points and detect unused methods.Run the skill to build the hypergraph for your workspace, generate the depth-4 module tree for your target crate and type, then rank each method by who_uses_summary fan-in to produce a dead-method list and top callers.
High-intent search queries and answers about installing and using this skill.
To find dead code in a Rust codebase, you can audit a specific type's public API surface to enumerate all methods and associated items, then compute per-method usage fan-in to flag any methods with zero call sites as dead code.
Checking Rust method usage involves running a fan-in analysis that summarizes who-uses data per method, ranking critical entry points by call-site count and distinguishing inherent methods from trait dispatch patterns.
Auditing a Rust type's public API surface for refactoring involves building a workspace hypergraph, generating a depth-4 module tree for the target type, and producing a dead-method list alongside top callers to prioritize cleanup.
Yes, detecting test-only helper methods in a Rust workspace is possible by computing per-method usage fan-in across the codebase, which flags methods that are only referenced within test modules and not used in production code.
Distinguishing inherent methods from trait dispatch in Rust requires analyzing call-site patterns across the workspace hypergraph to reason about how callers reach the API through impl blocks versus trait resolution.
The Rust method audit works across the entire workspace by building a workspace-level hypergraph, but the method-surface inventory and fan-in analysis target a single type within a specific crate to produce focused dead-code and refactoring summaries.
molacoAnalyze Rust enum variants and measure per-variant fan-in across the workspace.
kalpmodiAggregate phase summaries into a severity-clustered triage.md findings list.
CallMeLuigiv2Evaluate Rust polymorphism decisions between generics and trait objects.
knoopxIdentify unused files, dependencies, and exports in JavaScript/TypeScript projects.