rmc-snapshot-diff

Name: rmc-snapshot-diff
Availability: InStock
Author: molaco

Compares two network snapshots to identify structural and operational differences.

29|5|Updated Nov 24, 2025

Search Tags:#static analysis #rust #dependency coupling #workspace snapshots #api hygiene #complexity diff #cargo refactor

Ready to run

npx skills add https://github.com/molaco/rust-code-mcp --skill rmc-snapshot-diff

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: rmc-snapshot-diff
Source: https://github.com/molaco/rust-code-mcp/tree/main/skills/rmc-snapshot-diff
Command: npx skills add https://github.com/molaco/rust-code-mcp --skill rmc-snapshot-diff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you verify that a Rust refactor didn’t accidentally change public API surface, coupling between crates, or complexity characteristics across time.

Core Features & Use Cases

Compare two workspace snapshots to quantify deltas in item counts, visibility distribution, and API exposure.
Audit refactor impact by diffing dead-public reports, declared re-exports, and crate edge weights between two builds.
Validate complexity changes by comparing analyze_complexity output on the same files to flag potential regressions.

Quick Start

Run the skill with two prepared snapshot directories corresponding to branch-1 and branch-2 to produce a structured delta summary and verdict.

Frequently Asked Questions about rmc-snapshot-diff

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

FAQPage Schema

How do I detect Rust API surface and dependency coupling drift after refactoring?▼

To detect Rust API surface and dependency coupling drift, compare two workspace snapshots from different branches to quantify deltas in item counts, visibility distribution, and crate edge weights, providing evidence that structural invariants stayed intact during the refactor.

What is the best way to check for dead public items and complexity regressions in a Cargo workspace?▼

Checking for dead public items and complexity regressions involves diffing dead-public reports and analyze_complexity output between two builds, verifying that a Rust refactor didn't accidentally change public API exposure or introduce potential complexity spikes.

How do I compare two Rust workspace snapshots to audit refactor impact?▼

Compare two Rust workspace snapshots by running matching workspace_stats, dead_pub_report, crate_edges, and get_declared_reexports on each directory, then manually diffing the resulting JSON metrics to audit refactor impact and produce a structured delta summary.

Does comparing workspace snapshots require a dedicated hypergraph diff tool?▼

No, comparing workspace snapshots does not require a dedicated hypergraph diff tool because none exists; you must build hypergraph snapshots for each directory, run the analysis commands, and manually diff the resulting JSON metrics to evaluate refactor drift.

Can I validate complexity changes across two timestamps in a Rust project?▼

Yes, you can validate complexity changes by running analyze_complexity on the same files from two prepared snapshot directories corresponding to different timestamps, comparing this output to flag potential complexity regressions caused by refactoring.