A second look for the almost-right token
Catch the typo your linter reads right past
Context Check compares new GitHub diff tokens with the vocabulary already in your project—then explains the one character that looks out of place.
Free · Manifest V3 · Chrome, Edge, Brave · source never uploaded
The proof sheet
See what “almost” looks like.
This demo runs the same deterministic matcher as the extension. Edit either side; nothing is sent anywhere.
On every review
A quiet check, right where the change lives.
- 01
Open a GitHub diff
Context Check reads visible added and surrounding lines after the page loads.
- 02
Review a close match
A proof note names both tokens and describes the differing character or length.
- 03
Decide and move on
Fix the token, dismiss that exact pair, or disable a sensitive path. The choice stays local.
Install the preview
Download and unzip the package, open chrome://extensions, enable Developer mode, then choose Load unpacked. Pin Context Check for the paste-in proof sheet.
No cloud in the loop
Your source belongs to your project, not ours.
Matching happens entirely in the browser. Context Check has no analytics SDK, account, server, model API, or telemetry endpoint. Settings and dismissals use extension-local storage.
Read the plain-language privacy policy →Small print, plain words
Questions before you pin it.
Is this a spell checker?
No. It ignores prose. It looks for a new code-like token that is unusually close to a token already present in the surrounding repository context.
Does it diagnose dyslexia?
No. It is an accessibility-minded review tool for anyone who benefits from an explicit token comparison. It never evaluates a person.
Will it block a merge?
No. Version 1 adds review notes in your browser only. It does not change GitHub, your code, or CI status.
Can I exclude sensitive files?
Yes. The extension starts with patterns for environment files, secret directories, and PEM files. Add one path or wildcard per line in Review settings.