Most AI code reviews are vibes-based: nitpicks, no consistent bar, no guidance for
the author. This skill installs Google's documented engineering standard in two
modes that mirror the two audiences in Google's guide:
feedback.
The overarching rule is Google's: favour approving a change once it definitely
improves the overall code health of the system, even if it is not perfect. Seek
continuous improvement, not perfection.
This differs from a lint or static-analysis skill: it covers judgement, review
structure, comment wording, review speed and disagreement, not rule checking.
changes".
description, split a large change, or handle reviewer feedback.
emergency, how to resolve pushback, whether to approve with comments.
practices are broadly applicable.
Use a linter, type checker or CI skill when the question is "does this pass the
rules". Use this skill when the question is "should this change land, and how do
we talk about it".
No tools, accounts or network access. Inputs: the diff or files to review, and for
author mode the change being prepared. For a review, a missing description is
itself a finding: flag it before reading the code.
Review request goes to reviewer mode. "Help me get this ready" goes to author
mode. A general process question loads the matching reference from the upstream
repository listed at the end.
Read the description first, then look at the change in this order of importance:
design, functionality, complexity, tests, naming, comments, style, documentation,
every line, and the effect on the wider file and system.
Structure the review broad to narrow: does the change make sense at all, then the
files with the largest logical changes, then the rest. Optionally read tests first
to understand intent.
Comment rules:
Nit: for non-blocking polish, Optional: or Consider: forsuggestions, FYI: for information.
Review speed: respond within one business day, at a break point rather than
mid-task, because response speed matters more than total turnaround. Approve with
unresolved minor comments when the author can be trusted to address them. Ask for
a large change to be split.
Handling pushback: assume the author may be right, explain your reasoning if not,
stay polite, escalate when consensus fails, and never let a change sit because of
disagreement.
Emergency bar: only small changes fixing production bugs, security holes, legal
issues or a blocked major launch. Most "urgent" requests are not emergencies.
body explains why, the approach and the tradeoffs. "Fix bug" and "Phase 1" are
failures.
too large. Split by stacking, by file, by layer or by feature, keep tests in the
same change, and separate refactors from behaviour changes.
arguing, and never respond in anger.
A review is complete when it names the blocking issues, separates them from nits,
says whether the change should land, and gives the author something actionable per
point. Author help is complete when the description explains why and the change is
sized for one review pass.
User request: "Review this 900-line PR that mixes a refactor with a feature."
Inputs: diff plus a one-line description ("updates").
Expected result (illustrative):
Blocking: description does not explain why; the refactor and the feature should
be two changes; test coverage only on the feature path (design and tests fail).
Nit: helper name `doStuff2` is not communicative.
Verdict: not ready to land - split into a refactor CL and a feature CL, write the
description, then request review. Approve-with-comments would be wrong here.
cannot approve, merge or block a change by itself.
conventions wins over the generic advice, and personal preference still needs aNit: label.
differently.
Read-only. No repository writes, no branch operations, no network calls. Review
comments are produced as text for the user to post. Do not paste credentials or
private customer data from a diff into the review body.
and emergency policy:
This skill text is a derivative of Google's eng-practices documentation and is
distributed under CC BY 3.0, the same license as the source. It condenses and
restructures the original into reviewer and author modes and adds worked examples,
limitations and safety notes; the practices themselves are unchanged. The
attribution and full license text are in the LICENSE file next to this file.
correct rather than whether it should land.