Prioritize Rust refactoring by identifying complexity hotspots and estimating blast radius.
npx skills add https://github.com/molaco/rust-code-mcp --skill rmc-complexity
Please help me install this Agent Skill. Skill: rmc-complexity Source: https://github.com/molaco/rust-code-mcp/tree/main/skills/rmc-complexity Command: npx skills add https://github.com/molaco/rust-code-mcp --skill rmc-complexity
It helps you locate and prioritize gnarly Rust code by measuring cyclomatic complexity and then estimating how widely the impact of refactoring will propagate.
Ask for a workspace or crate complexity ranking by providing the crate name or a file path hint as an argument, then follow the suggested triage-to-validate workflow.
High-intent search queries and answers about installing and using this skill.
You can prioritize Rust refactoring by measuring file-level cyclomatic complexity to find hotspots, then estimating blast radius via call graph structure and usage summaries. This workflow highlights high-complexity functions with the widest structural impact across the workspace.
Cyclomatic complexity analysis in Rust workspaces triages large files and discovers gnarly code by aggregating total complexity and average per function. It identifies likely hot files that serve as primary candidates for targeted structural refactoring.
Find high-complexity Rust functions by first identifying hot files via complexity aggregates, then inspecting the call graph structure for dispatch-like functions with high out-degree. This pinpoints heavily connected functions within the most complex files.
This complexity analysis supports both a single Rust crate and a full workspace. Provide a crate name or file path hint as an argument to generate a complexity ranking and estimate the structural blast radius for your specific scope.
The best way to verify before and after complexity changes in Rust is by using snapshots. Capture initial file-level cyclomatic aggregates, perform your refactoring, then compare the new metrics to validate that the structural complexity has actually decreased.
Call graph indexing for Rust blast radius estimation requires using build_hypergraph to ensure proper structural mapping. Once indexed, combine this with usage summaries and caller recursion counts to accurately estimate how widely a refactoring impact will propagate.
molacoAudit a Rust workspace for coupling, dead code, and complexity.
Awannaphasch2016Profile code complexity and hotspots to guide targeted refactoring.
gganbukim1Identify dead code and complexity hotspots via graph-based analysis.
manuelbrandner85Parse source code into directed graphs for security-focused static analysis.
