Reviewable

Reviewable is a code review tool for GitHub pull requests that tracks what each reviewer has seen across rebases and sets merge rules in JavaScript.

Reviewable spares engineers from rereading code they already approved each time a change gets new commits. Ideanest LLC, an independent company trading as Reviewable, builds it, and its founder started the project after leaving Google. The tool opens any GitHub pull request in its own review interface, with sign-in through a GitHub account. Source code stays on GitHub, and only review metadata, comments and settings are cached. The Review Dashboard lists every open pull request with its reviewers, status checks and comment counts, and shows who needs to act next. Intelligent Line-Mapping keeps comments anchored through rebases, and per-reviewer incremental diffs show each person only what they have not yet seen. The file matrix and the discussion matrix show who has reviewed each file and where each thread stands. Every discussion carries a disposition such as blocking or satisfied, and it resolves only when nobody is still blocking it. Custom completion conditions written in JavaScript decide when a pull request may merge, and per-file ownership rules route files to the right reviewers. Reviewable suits engineering teams whose pull requests run long, get rebased often or need sign-off from several reviewers. Tech leads who enforce code ownership, readability or security review get rules in code that go beyond what GitHub's CODEOWNERS supports. Open source maintainers and individual developers use it on public and personal repositories. Companies on GitHub Enterprise Cloud or GitHub Enterprise Server can connect it there, or run it as an on-premises instance inside their own network. It is built for GitHub and only GitHub, so it fits teams whose code already lives there. A reviewer starts from the dashboard, opens the reviews waiting on them and works through the unreviewed files with keyboard shortcuts or deep links into VS Code and IntelliJ. Comments are drafted across the whole change and published to GitHub together, so the author gets one notification instead of many. Codecov coverage shows line by line inside the diff, and Slack carries review activity to each person as direct messages. Teams that build stacks of dependent pull requests with the spr tool review each one in order, with its merge status shown across the stack. Once the completion condition passes, the pull request merges, squashes or rebases straight from the review page.