Skip to content
MergeHarbor

Product

Index. Review. Verify. Learn.

MergeHarbor combines a continuously updated model of your codebase with an agent that investigates each pull request and checks its own work.

1 · Index

A map of your codebase, kept current

When you connect a repository, MergeHarbor parses it into a graph of files, functions, classes, and call relationships, builds a semantic index with plain-language summaries of each file, and builds a fast text-search index. After the first pass, only changed files are processed.

  • Symbol-level understanding for Go, Python, JavaScript, TypeScript, Java, Rust, Ruby, C#, C, and C++
  • Large binaries and generated or vendored code are skipped automatically
  • Reviews start immediately; indexing adds context as it completes
Repositories being indexed with per-repository progress

2 · Review

An agent that investigates like a senior engineer

For each pull request, the reviewer reads the change and then decides what else to read: callers of a modified function, similar code elsewhere, recent history of the file, and your team's rules. New code in the pull request is visible to its tools alongside the indexed codebase.

  • Follows changes across files and modules, not just the diff
  • Applies your rules, strictness, and categories
  • Very large pull requests are reviewed in parts and combined into one summary
Pull request detail with summary, confidence score, findings by file, and review history

3 · Verify

Every finding is challenged before it is posted

An independent verification pass tries to disprove each finding using the same codebase context. Findings that do not hold up are dropped; uncertain ones are posted with lower confidence. Filters for minimum severity and confidence keep reviews focused.

  • Fewer false positives, so engineers keep reading the comments
  • Confidence on every finding and a merge-readiness score on every review
  • Comments similar to ones your team rejected are suppressed
Overview of open critical and major findings across repositories

4 · Learn

Reviews that get closer to your standards over time

Engineers react to comments and reply in the pull request. MergeHarbor turns consistent feedback into proposed rules that an admin approves, and applies rules taught with @mergeharbor remember on the next review.

  • Rules scoped to paths and repositories
  • Approval workflow for learned rules
  • Knowledge base for design documents and conventions
Rules list with proposed rules awaiting approval

Also included

Everything around the review

Command palette

Jump to any repository, pull request, setting, or action from the keyboard.

Analytics

Bugs caught, time to merge, addressed rate, and comment ratings by team, repository, and author.

Usage and budgets

Cost per review and per developer, monthly budgets, and savings from model routing.

Audit log

Every change and sign-in, with export and streaming to your SIEM.

API and API keys

Automate setup and reporting with scoped API keys.

Every major code host

GitHub, GitLab, Bitbucket, and Gitea, cloud and self-managed.

Review every pull request with the context of your whole codebase

Connect a code host in minutes. Reviews start before indexing finishes.