Keep your linter. It's fast, cheap and great at enforcing rules. CodeReviewer covers what rules can't describe: whether the change is right for your codebase, your spec and your users.
| CodeReviewer | Linters & static analysis | |
|---|---|---|
| What it checks | Whether the change is correct in context: logic, data flow, security, conventions and scope | Whether code matches a fixed set of rules and patterns |
| Cross-file impact | Follows the change to callers, data paths and tests across the repository | Mostly file-by-file, or limited to rules that model cross-file flow |
| Your conventions | Learns them from your codebase and a small config file | Only what someone has written a rule for |
| Logic bugs | Catches errors like mixing cents and decimals, missed permission checks and off-by-one boundaries | Rarely. Logic errors usually follow every rule |
| Spec and requirements | Matches each pull request to the spec and flags what's missing | Not in scope |
| Explaining the problem | Plain-language findings with evidence and severity | Rule IDs and short messages |
| Fixing | Writes the fix, checks it compiles and commits it to the branch | Some auto-format or auto-fix for simple rule violations |
| Speed and cost | Minutes per pull request, per-developer pricing | Seconds, typically free and local |
| Beyond the code | Also writes and replays tests, and runs security and performance scans on the running app | Code only |
A linter answers “does this code follow the rules?”. A reviewer answers “is this change right?”. The second question needs context: what the rest of the code does, what the spec promised, what the data looks like. That’s the question CodeReviewer is built to answer.
Let your linter enforce formatting, imports and banned patterns in milliseconds. Let CodeReviewer read the whole change in context and tell you what a senior engineer would.
No. Linters are the fastest feedback loop you have and belong in the editor and in CI. CodeReviewer complements them and doesn't repeat what your linter already enforces.
It covers different ground. CodeReviewer flags security issues in context during review and adds passive and active scans of the running app. Keep any static scanning your compliance program requires.
It focuses on problems that need context. You can tell it which paths and patterns to ignore in the config file, and findings your team repeatedly dismisses are surfaced so they can be tuned out.
Start your 15-day free trial. We onboard a few teams every week.
