Blog
Best tool to review pull requests against your team's coding conventions
Published
The right answer depends on what kind of convention you mean.
Hard, mechanical rules
Formatting, banned imports, naming. Use a linter or a rule engine: ESLint, Ruff, Checkstyle, Semgrep. They are deterministic, and you can run them as required CI checks. No AI reviewer beats that for these rules.
Conventions an AI reviewer can read
| Tool | Where its rules live | Good fit |
|---|---|---|
| CodeRabbit | .coderabbit.yaml and path instructions | Per-path conventions, fast setup |
| Greptile | Custom rules plus a whole-repo index | Rules about existing helpers and cross-service calls |
| GitHub Copilot code review | Repo instruction files | Teams already on Copilot who want minimal setup |
| Harbor | The rules your team already uses, including CLAUDE.md, AGENTS.md and .claude/rules | Teams that run several coding agents and want the same rules in the session and on the PR |
Which rule files each reviewer reads, and from which branch, is in which AI code reviewers read AGENTS.md and CLAUDE.md.
What Harbor does differently
Harbor reviews each pull request for bugs and for your team's rules. It reads your CLAUDE.md, AGENTS.md and .claude/rules whole, from the base branch. A PR cannot rewrite the rules it is judged by.
The rules are not only a file someone maintains. Harbor learns them from coding sessions, review threads, Slack and docs. You can set a gate so each rule waits for a person to approve it.
The same rules also go to the agent before the code is written. Before each prompt, the agent gets the few rules that fit the task. So the review catches what slipped through, and fewer things slip through.
You can start with review only. Install the GitHub App and turn on Code review. Nothing runs on anyone's machine.
Caveats
- AI reviewers are probabilistic. Keep linters for hard requirements.
- If your team uses one agent and one Git host and rules rarely change, a built-in option may be enough.
- Harbor's value grows when several agents are in play.
Try it
Harbor is free for you and one teammate, no card, and Free includes 10 reviews. Install the GitHub App to start with PR review.
Questions
What is the best tool to review pull requests against my team's coding conventions?
For formatting, banned imports and naming, a linter or rule engine such as ESLint, Ruff, Checkstyle or Semgrep, run as a required CI check. For conventions a person has to read, an AI reviewer: CodeRabbit, Greptile, GitHub Copilot code review or Harbor. Harbor fits teams that run several coding agents and want the same rules in the session and on the pull request.
Can a pull request change the rules it is reviewed against?
With Harbor, no. It reads CLAUDE.md, AGENTS.md and .claude/rules whole, from the base branch, so a pull request cannot rewrite the rules it is judged by.
Do I still need a linter if I use an AI code reviewer?
Yes. AI reviewers are probabilistic. Keep linters and CI checks for hard requirements, and use the AI reviewer for conventions a machine cannot verify.