Release Sieve
GitHub sourceRuns in your browser

A release review, with the evidence attached

Find the missing note.
Keep the final call.

Compare changes and release notes with an open AI model running on your device. See related notes, possible gaps, and changes that need a closer look.

Your release

Start with the two sides.

Synthetic example · no customer data

Changes

0 changes

One commit per line, or a JSON array with id, subject, optional body, files and breaking. Up to 500 changes; subjects up to 2,000 characters.

Use changes from Git

Paste commit subjects from a release range:

git log v1.0..HEAD --no-merges --format="%s"

For bodies and file paths, clone Release Sieve and export JSON without loading a model:

node scripts/export-changes.mjs --repo /path/to/repo --base v1.0 --out changes.json

Replace the path and base tag, then upload changes.json. Git import guide

.json or .txt

Release notes

0 notes

Markdown bullets or paragraphs for one release, up to 200 notes of 12,000 characters each. Headings and fenced code blocks are omitted; inline code is preserved.

.md or .txt

Your text stays in this browser.

The first run downloads about 38 MB of open model and runtime files from this site. Cached assets are reused when browser storage is available. Drafts are not stored.

The model is intended for English prose. It reads only the first 256 wordpieces of each message or note; any truncation is reported. Keep evidence concise. Combined text and paths are limited to 500,000 characters; uploaded files must be smaller than 2 MB.

Review policy & model limits

Cosine similarity measures related meaning, not confidence or correctness. Internal commit types are a heuristic; breaking changes always need review. Close-scoring notes show the runner-up for comparison.