google-code-reviewer

Perform a structured code review by evaluating design, correctness, tests, readability, comments, and documentation to produce a verdict, numbered blocking findings, non-blocking suggestions, and a scope note. This approach assesses PR context, changed files, and risk profile to deliver high-leverage feedback.

Google-style code review triage is the process of quickly determining whether a change should proceed, requesting a split for oversized changelists, or surfacing major design concerns early. It prioritizes high-signal feedback and highlights blocking issues to ensure teams move forward confidently.

Yes, this Google-style review workflow is applicable for reviewers evaluating GitHub, GitLab, or Phabricator pull requests and changelists. It handles small to large changelists across these platforms, requiring triage, labeled findings, and high-leverage feedback based on the PR context.

Code review findings are labeled by severity as Required, Nit, Optional, or FYI. This multi-dimensional evaluation categorizes blocking findings and non-blocking suggestions separately, allowing reviewers to assess design, correctness, concurrency, performance, naming, comments, docs, and style effectively.

The best way to review oversized pull requests is through structured triage that quickly surfaces major design concerns and requests a split for oversized changelists. This high-leverage review workflow assesses scope and risk profile early, ensuring consistent evaluation of large changes.

A structured code review produces a clear Verdict, numbered Blocking Findings, Non-Blocking Suggestions, Positives, and a Scope Note. This reusable review-output-template format ensures high-signal feedback that highlights blocking issues and prioritizes high-leverage improvements for the team.