Skip to content

Small diff. Bigger picture.

Understand every change before you merge.

Review pull requests, spot potential issues, and check changes against your team’s architecture rules—with clear explanations grounded in your code.

Get started with GitHub

Your code. Your rules. Your call.

DiffveraPull request review
Sample review

EXAMPLE REPOSITORY / ORDER SERVICE

Add order details endpoint #42

TypeScript 1 potential issue
orders.ts
Changed file

src/services/orders.ts

TypeScript code excerpt, lines 24 to 30. Line 28 looks up an order by ID without checking user ownership.

export async function getOrder(  orderId: string, userId: string) {  return db.order.findUnique({    where: { id: orderId },  });}
Architecture context: service data layer
High severity Security L28

An order ID isn’t an ownership check.

This query filters by orderId alone. If the caller can supply another order ID, this endpoint could expose another customer’s order.

Evidence · userId is accepted at line 25 but never used in the lookup at line 28.
Suggested correction

Scope the lookup to the authenticated owner:

db.order.findFirst({
  where: { id: orderId, ownerId: userId },
});

Get userId from the server session and handle a missing order before returning a response.

Grounded in the diff. Explained in context.Suggestions for your team to review.

A sample of the review experience. Clear context, evidence, and a way forward.

How it works

From pull request to a clearer next step.

A second perspective on your code. A decision that stays with your team.

  1. 01

    Bring your repository.

    Connect GitHub and choose which repositories Diffvera can access. Keep the review close to the code.

  2. 02

    Choose the change.

    Pick a pull request and request a review when you need one. Your team sets the pace.

  3. 03

    Make an informed call.

    Read the findings, follow the evidence, and assess the suggested corrections. You decide what happens next.

You review the suggestions. Your team owns the merge.

A closer look at the change

A review you can reason with.

Correctness, security, and architecture—with the context to understand why a finding matters.

Correctness

Follow the logic.

Look at how the change behaves, including the edge cases that are easy to miss in a busy pull request.

  • Boundary conditions
  • Missing checks
  • Failure paths

Security

Question the access.

Examine who can reach the data and which assumptions the code makes about identity and input.

  • Ownership checks
  • Input handling
  • Data exposure

Architecture

Respect the boundaries.

Check the change against your team’s rules, so a small shortcut doesn’t become a lasting dependency.

  • Layer dependencies
  • Module boundaries
  • Team conventions

Context you can follow back to the code.

File paths, line references, explanations, and suggested corrections.

See it in the sample review

Your architecture, in the review

Good boundaries deserve a second look.

Make your team’s architecture rules part of the conversation. Trace a potential violation to the change that introduced it, with an explanation you can act on.

Example team rule

Service modules must not import controller modules.

Keep business logic independent of the HTTP layer.

Your team defines the boundary. The review brings the evidence.

Architecture example

Sample finding

src/services/orders.ts

import { orderController }  from '../controllers/orders' export async function loadOrder(id: string) {  return orderController.findById(id)}
Layer dependencyL12–13

The service reaches into the controller.

This import makes business logic depend on the HTTP layer, crossing the boundary defined by the team’s rule.

Suggested direction

Move the lookup behind a repository. Let the controller call the service.

import { orderRepository }
  from '../repositories/orders'

controller service repository

A few useful answers

Before you dive in.

A clear workflow. A second perspective. Your team in control.

Which repositories can Diffvera access?

Choose the repositories available to Diffvera when installing the GitHub App. Repository access follows the selection you make for your team.

How do I start a review?

Select a pull request in a connected repository and manually request a review. You choose the change and when to review it.

Will Diffvera change my code or merge a pull request?

Diffvera provides findings, explanations, and suggested corrections. It does not automatically modify code or merge pull requests. Your team decides which suggestions to apply and when to merge.

What does an architecture finding mean?

It highlights a change that may conflict with a rule defined by your team, such as a dependency crossing a layer boundary. Assess the rule, the relevant code, and the explanation together.

What if I disagree with a finding?

Use the evidence to assess the finding in context. Mark findings useful, false positives, or resolved as part of your review. The decision stays with your team.

Your next pull request

Bring clarity to your next merge.

Review the change. Understand the reasoning. Decide with your team.