Review a Pull Request Locally Before You Merge It
Get a second pair of eyes on your code changes with a free, open-source editor assistant and a model that stays on your computer.
ToolContinue (open-source IDE assistant, Apache-2.0)
Cost$0 — open-source licence (Apache-2.0)
LimitsYour hardware is the limit when run with a local model
Verified8 October 2026
Why this works
A solo developer or a two-person team often merges without review. A local model is not a replacement for a human reviewer, but it catches the obvious: unused variables, missing error handling, and tests that do not run.
Step by step
- Check out the branchUse git to switch to the pull request's branch locally and view the diff.
- Select the changed filesAdd only the changed files to the assistant's context so the review stays focused.
- Run the review promptUse the prompt below and ask for findings with file and line references.
- Verify each findingReproduce or reject every finding. Do not accept a suggestion you do not understand.
- Run the testsRun the project's test suite and linter yourself; the model is not a test runner.
Copy-paste prompt
Review this diff as a careful senior engineer. List only concrete problems: bugs, missing error handling, unclear naming that affects behaviour, and missing tests. For each, give the file, the line, the problem, and a one-sentence fix. Say 'no issues found' if none. DIFF: <paste>
Check your result
- Every finding is reproduced or rejected
- Tests and linters were run by you
- No code was merged on the model's word alone
Pitfalls to avoid
- Models produce plausible but wrong findings; treat them as leads.
- Keep private repository code on local models, as the workflow above does.
What we checked: Licence and project status were read from the project's GitHub repository on 8 Oct 2026. Install commands and flags change between releases, so follow the project README for the current version. Source: https://github.com/continuedev/continue.