An icon set starts as one grid, one stroke width and one naming convention. Then a 20px icon arrives from a different file, a hurried export leaves a 1.5px stroke, somebody adds CheckMark.svg next to arrow-left.svg, and a second copy of the back arrow appears under a new name. Every one of those renders fine on its own. Together they are no longer a set.
This walkthrough uses the tool's public README and checked-in example files. Run the command from a repository checkout with Node.js 22+; inspect the source before using it on your own files.
Run the checked-in example
git clone https://github.com/edilec/icon-set-consistency-checker
cd icon-set-consistency-checker
node bin/icon-set-consistency-checker.mjs --root examples/clean --policy icon-policy.jsonRead the result
Both run under npm run check, so an example that drifts from the tool fails the build.
Where this check stops
Every bound is enforced and reachable from the command line, and no bound is ever a silent truncation.
Before adapting the command to your own workflow, review the accepted inputs, exit codes and safety boundaries in the README.
Compiled with AI assistance from checked-in public documentation and example scripts. Run the example and review the repository's current documentation before relying on its result.