studio-seventeen
WORKSHOP--:--
~/workshop/skills/modbus/compare-maps.md

$compare-maps

SKILL 11 / 20READ-ONLY

Compare Maps

Compare two map versions and show which points were added, removed, moved, changed, or left unresolved.

WHAT YOU GET

A clear result you can inspect

It writes `diff.json` without changing either map. Use it to compare manuals, device models, or firmware versions. It reports points that were added, removed, moved, or changed, including address, data type, scale, byte order, bit numbering, and source changes.

HOW IT RUNS

Matches points before it compares fields

01 · GUIDESKILL.mdprocess + safety
02 · EXECUTEscripts/run.pybundled local Python

Matches points before it compares fields. The script first puts both inputs into the standard map format. It identifies a point by its device route, unit, register area, address, and logical name instead of by address alone. Every point from both maps appears in the comparison report.

WHERE IT FITS

Used in these workflows

EXAMPLE REQUEST

Ask for the result in your own words.

Use this example as a starting point. Replace the file names and details with your own.

CODEX$compare-maps
CLAUDE CODE/modbus-skills:compare-maps
CURSOR + OTHER CLIENTSUse the client’s native skill invocation.
$compare-maps

Compare `firmware-2-map.json` with `firmware-3-map.json`. Show me which points were added, removed, moved, or changed, including changes to scaling and byte order.
GitHub source ↗