Rank supplied context items by configured authority, declared relevance, freshness and resolved evidence links, and explain every score — so that a retrieved page cannot outrank the instructions, and a governing document that has quietly gone out of date is reported before it is obeyed again.
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/context-priority-ranker.mjs \
--root examples/assembled \
--policy examples/policy.json \
--today 2026-09-14Read the result
Two warnings, because the page uses two of the listed phrases. The finding lines are ordered by (file, pointer, ruleId, message) rather than by severity, so a report reads against the document. Every line above is a line the CLI writes, character for character; what is left out is the status header, the counts and the explanation each WARN line carries underneath it. test/examples.test.mjs asserts exactly that, so the block cannot drift.
Where this check stops
Each is enforced, named in the finding that reports it, and reachable from the command line. Reaching one is an incomplete run, never 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.