What it proves
A small public tool can be valuable when it shortens a recurring scan into one concrete output shape without pretending to replace the later judgment call.
Workflow checks
release-note-diff-cli shows how a tiny check can compress a noisy review task into one visible shortlist.
This guide exists because release-note review is a good example of repeated workflow drag: the raw material is long, the important changes are usually sparse, and the first useful output is a compact shortlist rather than a full analysis layer.
Why this repo carries the track
A short site-side guide before the proof layer on GitHub.
Why it matters in this track
It shows the workflow-check pattern in a different setting: not docs cleanup, but repeated review work where the first job is to surface what changed and what might matter.
What survives the first run
The additions shortlist is the artifact. It gives the next review step a much smaller surface area to inspect.
What the first useful success looks like
release-note-diff-cli as a first useful success, not only a demo.
The first useful run is a tight scan result that highlights which additions deserve attention. That makes the second move obvious: read the few changed items that are most likely to affect your product or workflow.
Use this when recurring release-note review should start with a shortlist, whether the follow-up is product analysis, platform planning, or customer guidance.
python3 release_note_diff.py sample_old.txt sample_new.txtAdded: 2
Removed: 0
Important additions: 2
Important additions:
- Launched detached invocation support
- Fixed retry bug in function executorWhere it routes next
CLI that diffs release notes and highlights additions likely to matter.