Yard Docs
Sign in
On this page

Reviewing a large pull request

The review digest of a finished project: what changed, what to read closely and what can wait, what to do before deploying, and the plain diff one tab away.

Updated November 2, 2026 ยท 3 min read

The digest is off until you turn it on: when a project reaches Review, its Changes tab has a Review digest link to Turn on review digest, and Turn off digest beside the digest's tabs switches it off again. The choice is kept in this browser, and the runner does no analysis for a project nobody asked it for.

Once on, it shows the pull request read for review. It has three tabs, and the one you pick is kept in the address (?review=brief, structure or diff):

  • Review brief: how big the change is and how much of it to read closely, what changed in plain words, what to do before deploying, the changes to read first, and everything else.
  • Changes by structure: every change as a row, grouped by what it needs, with a detail panel beside the table.
  • Plain diff: exactly git diff <merge base> <head> of the branch, file by file. Every fold in the other tabs opens to its lines here.

How it is measured

The analysis runs on your runner, in the project's box, once per commit. It does not ask a model, so the same commit always gives the same digest.

  • By structure. TypeScript, TSX, JavaScript, Rust, Go, Python, HCL (Terraform), SQL, JSON, YAML and TOML are parsed with tree-sitter and compared symbol by symbol: functions, methods, classes, routes, Terraform blocks, config keys. A file in another language, or one that fails to parse, is listed as Lines and is never folded. The page names those files.
  • Folds need a proof. A change is folded only when a rule shows it is safe to skim, and the rule is shown with it: comments or whitespace only, the same body under a new name, a file renamed with the same hash, the same edit repeated identically, a generated file, a lockfile whose packages match the manifests, a Drizzle snapshot whose tables are all created in the pull request's SQL. When the proof does not hold, the file stays in Read first with the reason.
  • Read first holds changes to existing code, riskiest first. The score is the kind of change, times how many places call it, plus a bonus for paths under auth, middleware, security and migrations.
  • Reach says who calls a changed symbol and how that was counted: by text at a named commit, not checked one by one.

Before you deploy

New migrations, env variables added or no longer read, new cron schedules, new public routes, compose and Dockerfile changes, Terraform version constraints, renamed or removed inputs, removed modules and upgrade guides, each with its files. Copy as checklist copies them as Markdown.

Read ticks

Tick a change when you have read it. Ticks are yours: nobody else sees them, and nothing ticks a change for you. A tick clears itself when a later commit changes that change. In Changes by structure, j and k move between rows, Enter opens one and x ticks it.

The agent

When the digest is ready, the project's agent is asked once for the What changed bullets and one sentence per change to read first. Each points at the changes it comes from. The agent cannot fold, order or tick anything, and when it fails the brief shows without its words.

Ask about this on a change, or Ask the agent above the table for the whole pull request, puts it in the Agent composer as a chip. Your next message carries that change's paths, lines and reach to the agent.

Was this page useful?
Edit this page