Wire
Check every pull request against your team’s rules.
Harbor reads each pull request, checks it against your repo’s rule files and your team’s brain, and comments on the lines that break a rule. It checks rules. It is not a general bug review.
Turn it on
Install the Harbor GitHub App
An admin opens Sources in the web app and presses Connect on GitHub. Pick the repos it may read. If your organization needs an owner to approve new apps, GitHub sends them your request. Once they approve it, come back to Sources and connect it.
Turn on Code review
Open Code review in the sidebar and turn on Review pull requests. It is off until an admin turns it on, and installing the app alone starts nothing.
Open a pull request
Harbor waits about two minutes so that a burst of pushes makes one review, then posts a check named Harbor review, a summary comment, and a comment on each line that breaks a rule. Most reviews take under three minutes after that.
What it checks against
- The repo’s rule files, read as they were before the pull request, so a pull request cannot rewrite the rules it is checked against: CLAUDE.md, AGENTS.md, Cursor and Copilot rules, and CONTRIBUTING.md. See which agent reads which rules file.
- Your team’s brain, on private repos only.
A repo with neither gets a check that says nothing to check. Commit a rule file with your team’s rules to the base branch, then ask for a review.
When it runs
By default, on every pull request when it opens or is marked ready for review. On the Code review page you can limit it to the repos you pick, run it only when someone asks, or run it again on each push. Anyone on the team can ask on a pull request:
@harbor-brain reviewThe Re-run button on the check does the same.
Two kinds of pull request are reviewed only when someone asks:
- Dependency updates from Dependabot and Renovate.
- Pull requests from a fork of a public repo, opened by someone outside your team. Otherwise anyone on the internet could spend your reviews.
Pull requests from your coding agents are reviewed like anyone else’s. They are who this is for.
What the check says
| Check | What it means |
|---|---|
| Rules checked, none broken | Green. Every reviewer answered, and no rule was broken. |
| Team rule broken | Grey. A comment sits on each line, and the summary lists them. It never fails the check. |
| Partial review | Grey. Part of the review did not run, and the summary says which part. |
| Nothing to check | Grey when no rules were found. Green when the pull request only changes lockfiles and other generated files. |
| Not reviewed | Grey. The check says why: the settings, the monthly limit, or who opened it. |
| Did not finish | Grey. The check says why, and what to do next. |
Harbor never fails a check in this version, so a broken rule informs the merge and does not block it.
Holding a merge until the review has run
Turn on Block merging until the review finishes, then in each repo’s branch rules on GitHub, require the status check named Harbor review. Harbor cannot change branch rules for you.
The check then appears the moment a pull request arrives. It always completes, even when no review will run, so it holds a merge for a review and never for one that is not coming.
What it costs
Each workspace gets $5 of reviews a month on Harbor’s model key. The Code review page shows what you have used. A typical review costs between one and twenty-five cents.
Past $5, a pull request gets a check saying it was not reviewed, and reviews start again on the first of next month. To keep going before then, add your own Anthropic key on the Code review page. The review then runs on your account and the limit no longer applies. Harbor tries the key before saving it, stores it encrypted, and never shows it again.
What happens to your code
- Each review runs in its own short-lived task, which clones the repo with a token that works on that one repo and expires within the hour, and exits when the review ends.
- The changed code and the parts of the repo the review reads go to Anthropic, under Harbor’s key or yours, to run the review.
- Harbor keeps a record of each review: the pull request’s title and number, the result, the kind of each finding, its file and line, the time and the cost. It keeps no code and no model text.
- Nothing is committed to your repo. Harbor posts comments and a check, and that is all it writes.
Next, how the rules get into the brain in the first place: connect GitHub, Slack and Notion as sources.