# Everything the review agent does for your team

One agent reads your codebase, reviews every pull request, and checks its own work. These are the parts you can turn on, tune, and build on.

## Codebase-aware review

MergeHarbor indexes each repository, follows what depends on the code a pull request changes, and tries to disprove every finding before it posts a comment.

[Codebase-aware review](https://mergeharbor.com/features/review-agent)

## Merge gate

The merge gate combines findings, proof runs, requirements, tests, change risk and approvals into one verdict, a readiness score from 0 to 100 and a checklist of what to fix.

[Merge gate](https://mergeharbor.com/features/merge-gate)

## Rules and learning

Write rules in plain English, keep them next to the code they govern, and let MergeHarbor learn from how your team responds to its comments. You can see and undo what it learns.

[Rules and learning](https://mergeharbor.com/features/learning)

## Free security checks

Before a model reads the change, built-in rules look for committed secrets, injection risks, unsafe settings and risky migrations. These checks use no model and no credits.

[Free security checks](https://mergeharbor.com/features/security-review)

## Proof runs

After a review, MergeHarbor writes small tests that try to reproduce its findings, runs them in an isolated sandbox against your pull request, and attaches the evidence to the findings it proves.

[Proof runs](https://mergeharbor.com/features/proof-runs)

## CLI and local reviews

The mh command line reviews the changes on your machine with the same rules, configuration and codebase context as pull request reviews. Nothing is posted to your code host.

[CLI and local reviews](https://mergeharbor.com/features/cli)

## Coding agents and MCP

Every review comment has buttons for the coding agents your team uses. Plugins and an MCP server let agents review your branch, fix findings and check again until the review is clean.

[Coding agents and MCP](https://mergeharbor.com/features/coding-agents)

## Context connectors

Connectors bring in the tickets, docs and production errors a pull request points to. MergeHarbor checks the change against the ticket's acceptance criteria, reads linked specs, and flags code behind recent errors.

[Context connectors](https://mergeharbor.com/features/context)

## Slack, Teams and Google Chat

Mention @MergeHarbor in a Slack, Microsoft Teams or Google Chat thread to ask about a pull request, summarise its review, explain a finding, or open a fix pull request behind a confirm button.

[Slack, Teams and Google Chat](https://mergeharbor.com/features/chat-apps)

## Change risk

Every review scores a pull request's risk from 0 to 100 and says why, shows which changed code your tests miss, and flags migrations and API changes that can break production.

[Change risk](https://mergeharbor.com/features/change-risk)

## Models and costs

MergeHarbor runs every review on its own models, picks the right one for each step, and shows what each review cost. No model keys to supply or pay for.

[Models and costs](https://mergeharbor.com/features/costs)

## Security scans

Security scans check the default branch for secrets, vulnerable dependencies, risky configuration and dangerous code patterns. Every finding is checked a second time before you see it.

[Security scans](https://mergeharbor.com/features/security-scans)

## Vulnerabilities

MergeHarbor keeps an inventory of every repository's dependencies, matches each version against its vulnerability database, ranks findings by severity, exploit activity and reachability from your own code, and routes them to the team that owns them.

[Vulnerabilities](https://mergeharbor.com/features/vulnerabilities)

## Issue triage

MergeHarbor reads new issues in Jira, Linear, Asana, GitHub and GitLab and keeps one comment on each, with possible duplicates, questions for the reporter, acceptance criteria and triage suggestions.

[Issue triage](https://mergeharbor.com/features/issue-triage)

## Insights

Insights shows time to merge, review quality, security findings, merge gate verdicts and adoption, with the same filters on every view, exports and a read-only API for BI tools.

[Insights](https://mergeharbor.com/features/insights)

## Shipyard

Shipyard is MergeHarbor's coding agent. Give it a task and it drafts a plan for you to approve, makes the change in an isolated sandbox, runs your tests and lint, and opens a pull request that MergeHarbor reviews.

[Shipyard](https://mergeharbor.com/features/shipyard)

## MergeHarbor Agent

Run automations on a schedule or when something happens, and talk to MergeHarbor in Slack, Microsoft Teams, Google Chat or Discord. Code changes go to Shipyard, the coding agent.

[MergeHarbor Agent](https://mergeharbor.com/features/agent)

## Review every pull request with the context of your whole codebase

Connect a code host in minutes. Reviews start right away, and codebase context is added as indexing completes.

[Start free trial](https://app.mergeharbor.com/signup) [Book a demo](https://mergeharbor.com/contact?topic=sales&source=demo)