Diff-based review starts from the actual change

A diff review checks files, scope, behavior, tests, configuration, and accidental changes. An AI-generated summary can help orient the reviewer but cannot replace reading the actual diff.

Start with the file list, then inspect the causal path and verification evidence.

Review passFocus
L1 scopeUnexpected files and unrelated changes
L1 behaviorChanged branches, errors, and contracts
L1 testsCoverage of the changed behavior
L1 operationsConfig, scripts, permissions, and generated output

Diff review sequence

  1. Read the task and acceptance criteria.
  2. Inspect the changed-file list.
  3. Review the diff by behavior, not only by file.
  4. Check tests and configuration.
  5. Compare claims with commands actually run.
  6. Return findings with file:line and evidence.
  7. Record no-findings with scope and limits when appropriate.

Review note

Scope checked: <paths>
Unexpected files: none / <list>
Findings: <list or none>
Checks observed: <commands>
Unknowns: <limits>
Decision: accept / revise / hold

Canonical lesson source · JavaRush

Open JavaRush material