Media
1 item
Description
Warns before you approve a GitHub pull request that still has unreviewed files. Review Guard catches the moment code review turns into rubber-stamping: clicking Approve on a pull request before you've actually opened every changed file. On GitHub's own "Files changed" page, GitHub already tracks which files you've marked "Viewed." Review Guard watches for exactly one thing: you selecting Approve and clicking Submit review while any changed file is still "Not Viewed." When that happens, it shows a small on-page warning with two choices — jump straight to the first unreviewed file, or approve anyway if you're confident you don't need to. How it works: 1. Open any GitHub pull request's "Files changed" tab. 2. Review as usual, marking files "Viewed" as you go. 3. Click "Submit review" and choose Approve. 4. If files remain unreviewed, Review Guard pauses the submission and asks — "Review remaining files" or "Approve anyway." Privacy and scope: - Runs only on github.com pull request pages. - Reads only the review selection and per-file "Viewed" state GitHub already shows on the page. - Never submits a review, comment, or approval itself — both warning choices only replay GitHub's own Cancel and Submit controls. - No network requests, storage, analytics, accounts, advertising, or remote code. Review Guard does one narrow job: make sure "Approve" means you actually looked.
rating_count is the Chrome Web Store ratings count, not a written-review count.