rmc-mut-static-audit

To audit Rust global mutable state, this Skill locates local `static` items matching `static mut`, `LazyLock<...>`, `OnceLock<...>`, and `OnceCell<...>` patterns across your workspace. It builds a hypergraph to map these singletons and reports their locations and types for architectural review.

Assessing singleton dependency impact before refactoring Rust code requires tracking how many call-sites use each global. This Skill runs `who_uses` and `who_uses_summary` per finding to quantify architectural coupling and removal difficulty for your workspace globals.

Finding `static mut` and lazy initialization patterns in a Rust project requires type-aware workspace matching. This Skill executes `mut_static_audit` after building a hypergraph to identify HIR types matching `static mut`, `LazyLock`, `OnceLock`, and `OnceCell` and reports their exact file locations.

Yes, you need to build a hypergraph before running a global state safety audit. The Skill requires executing `build_hypergraph` first to map workspace dependencies and call-sites, which enables the subsequent `mut_static_audit` and `who_uses` analysis.

You can review the source context of global mutable state findings during a Rust architecture triage by running `read_file_content(file_path=...)`. This pulls the relevant source file region around each finding span to inspect initialization and documentation.