This offline reporter groups a saved local Git-history export by package and feature and points out changes that merit release-note review. It is useful when a reviewer needs a compact, repeatable view of a history snapshot without running Git or publishing history text. It does not decide that a release note is missing.
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
node bin/commit-scope-summarizer.mjs --root examples/clean --input input.json
node bin/commit-scope-summarizer.mjs --root examples/failing --input input.json
node bin/commit-scope-summarizer.mjs --root examples/incomplete --input input.json --json
npm run checkRead the result
The first example exits 0, the second exits 1 with a review candidate, and the third exits 2 because a revert target is absent. --help prints usage. The default CLI writes one JSON report to stdout and a fixed count summary to stderr; --json suppresses only that summary. No report file is written.
Where this check stops
This local walkthrough does not establish the state of a live production system or replace the limits documented in the repository.
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.