Classify Rust symbol references into test-only or production categories.
npx skills add https://github.com/molaco/rust-code-mcp --skill rmc-test-vs-prod
Please help me install this Agent Skill. Skill: rmc-test-vs-prod Source: https://github.com/molaco/rust-code-mcp/tree/main/skills/rmc-test-vs-prod Command: npx skills add https://github.com/molaco/rust-code-mcp --skill rmc-test-vs-prod
It helps you determine whether a Rust symbol (or family of related symbols) is only used in tests or is truly part of the production code path, so you can prioritize refactors and reduce high-touch change risk.
Type::new-style constructors and trait/public API entry points to find candidates for demotion, #[cfg(test)], or fixture extraction.Ask your AI to analyze a specific symbol by running who_uses_summary for the target after building the hypergraph for the repository.
High-intent search queries and answers about installing and using this skill.
To check if a Rust symbol is test-only versus production, you classify reference categories into Test and Other. This categorizes each reference as Read, Write, Test, or Other to judge whether usage is test-only, production-only, mixed, or over-tested.
Auditing Rust constructors for refactoring involves classifying usage for Type::new-style constructors and public API items. This identifies candidates for demotion, cfg(test) isolation, or fixture extraction based on test-only or production-only verdicts.
rust-analyzer works with test coverage analysis by building the HIR hypergraph and running who_uses_summary. Interpreting the category_breakdown outputs a test-only, production-only, mixed, or over-tested verdict for targeted symbols.
To identify diffuse invariants from heavy write fan-in, you analyze Read and Write sub-counts for Rust symbols. This encapsulation signal flags symbols with heavy write fan-in, indicating potential invariant management issues.
The limitations of using heuristics for Rust refactoring triage include potential inaccuracies in reference classification. The analysis provides notes about heuristic limitations alongside actionable output like verdicts, counts, top consumers, and recommended actions.
molacoAnalyze Rust function caller and callee relationships across a workspace.
tanghuoRefactor Go code to remove test-driven abstractions and preserve runtime semantics.
blackwell-systemsIdentify all call sites of a library symbol across multiple repositories.
LerianStudioDetect testing anti-patterns in codebases during test reviews and CI validation.