Reviews that know what the change is meant to do
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.
Requirements: PAY-12
Met Refunds cannot exceed the original charge pay/refund.go:42 Met Partial refunds are written to the ledger pay/ledger.go:88 Not met The customer is emailed when a refund completes No change in this pull request sends the email
Docs read: Refund policy (Notion) This change touches code behind Sentry issue API-4F.
How it works
Connect your tools
Under Memory → Integrations: Notion, Confluence, Google Drive and OneDrive for docs; Jira, Linear and Asana for tickets; Sentry and Datadog for errors.
Link the work
MergeHarbor finds ticket keys such as ENG-123 and links to tickets and docs in the branch name, title, description and commit messages. Only linked or pinned items are read.
Review against requirements
Each acceptance criterion is marked Met, Not met or Unclear in the review summary, with file:line evidence from the pull request.
What you get
- No extra model call
- The requirements check is part of the review. Ticket and doc text adds at most 3,000 input tokens by default, and nothing when nothing is linked.
- Linked or pinned docs
- Notion pages, Confluence pages linked from Jira, and Google Drive or OneDrive files linked from the pull request or its tickets, or pinned for a repository.
- Production errors in view
- When a change touches files in the stack frames of recent Sentry or Datadog errors, the reviewer is told and the summary says so. Reviews never wait for them.
- Nothing is crawled
- Connectors read only what a pull request or its ticket links to, or what an admin pins. Google Drive uses drive.file, so MergeHarbor opens only files you pick.
- Optional status comment
- For Jira, Linear and Asana, turn on write-back and MergeHarbor keeps one comment on each linked ticket, updated after every review. It is off by default.
- Sources cited
- A comment that relied on a ticket, page or file says so and links to it. The requirements check lists the docs the review read.
Frequently asked questions
What if the ticket has no acceptance criteria?
MergeHarbor lists up to three requirements it inferred from the description, labelled "(inferred)". If no ticket is linked, it can look for related Jira or Linear work and use it as background only.
What does MergeHarbor store from these tools?
Ticket and doc text is redacted of secrets, cached for a short time, deleted within 24 hours and never written to logs. Tokens are encrypted at rest and never shown again. Disconnecting deletes tokens and cached text.
Does MergeHarbor write to our tracker?
Only if you turn on write-back for Jira, Linear or Asana. It then asks for comment permission and keeps one status comment per linked ticket. Docs and observability connectors are read-only.
Have another question? Ask our support team
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.