5 items
Review agent-authored GitLab merge requests by what matters: the ask, deviations, decisions, validation gaps and security findings. Coding agents write more code than people can read line by line, and much of it doesn't need reading. ReviewLab opens a GitLab merge request in a review page that shows what needs your judgement first. • The ask: what was asked for, summarized by the agent, next to what it delivered. • Deviations: where the agent did something other than what was asked, and why. • Decisions: questions the prompt left open, what the agent chose, and the alternatives, each with a prompt you can hand to an agent. • Verification: what the agent ran to prove the change works, with evidence, and what it couldn't validate. • Security: findings from a separate reviewing agent, with a patch to apply or a prompt to fix them. • Rollout: what still has to happen before and after merging. • Focus ranking: test coverage of the changed lines, complexity, risk signals and the reports above rank every file as Focus, Skim or Skip, so you read the files that matter and skim the rest. Review without leaving the page: turn findings into draft comments with suggested changes, submit them as one review, approve and merge. Click "Open in ReviewLab" on any merge request on gitlab.com, or the toolbar button on any GitLab instance. Try the demo merge request on the start page; no setup needed. Works with gitlab.com and self-managed GitLab: set your GitLab URL in the settings, and Chrome asks for access to that one host. Reports are published as merge request notes by the authoring agent, a security reviewer and CI. Set a project up with the ReviewLab CLI and Claude Code plugin: https://gitlab.com/wearethefoos/reviewlab Add a GitLab personal access token in the settings (read_api to read, api to submit reviews and merge). It stays in your browser and is only sent to your GitLab instance. ReviewLab has no servers and collects no data. Open source under the Apache License 2.0.
Nov 7, 2026
rating_count is the Chrome Web Store ratings count, not a written-review count.
Media assets
Screenshots and videos on the listing.
Has promo video
Whether the listing includes at least one video.
Languages
Declared language locales.
Developer website
Listing exposes a developer website URL.
Contact email
Listing exposes a contact email.
Keyword in name
Case-insensitive substring match in the name.
Keyword in description
Case-insensitive substring match in the description.
Keyword occurrences in description
Count of case-insensitive occurrences in the description.
Category user-count percentile
Share of same-category extensions with fewer users (null if unknown).
These are transparent listing completeness / keyword signals, not a prediction of Chrome Web Store search ranking.