explaingit

google/eng-practices

★ 20,548Audience · developerComplexity · 1/5StaleLicenseSetup · easy

TLDR

Google's public engineering practices documentation, including detailed code review guidelines for reviewers and change authors.

Mindmap

mindmap
  root((repo))
    What it does
      Code review guides
      Best practices
      Engineering standards
    Key concepts
      Changelist CL
      LGTM approval
      Reviewer guide
      Author guide
    Use cases
      Improve code reviews
      Train teams
      Set standards
    Audience
      Open source projects
      Engineering teams
      Organizations

Things people build with this

USE CASE 1

Establish code review standards and processes for your engineering team.

USE CASE 2

Train new developers on how to write better change descriptions and respond to feedback.

USE CASE 3

Create organizational guidelines by adapting Google's practices to your project's needs.

Getting it running

Difficulty · easy Time to first run · 5min
Use and share freely with attribution; you must credit Google and can modify for your own use.

In plain English

This repository contains Google's Engineering Practices documentation, which covers generalized engineering practices developed across all languages and projects at Google. The documentation is published publicly so that open source projects and other organizations can benefit from Google's accumulated experience. Currently it contains Google's Code Review Guidelines, which consists of two separate guides: the Code Reviewer's Guide and the Change Author's Guide. The documents use some Google-internal terminology, including CL (changelist, equivalent to a change, patch, or pull request) and LGTM (Looks Good to Me, used when a reviewer approves a CL). The documents are licensed under CC-By 3.0.

Copy-paste prompts

Prompt 1
Summarize Google's Code Reviewer's Guide and give me 5 key principles I should apply to my team's pull request reviews.
Prompt 2
What does Google recommend for writing good change descriptions? Give me a template based on their Change Author's Guide.
Prompt 3
Extract the most important dos and don'ts from Google's code review guidelines that apply to small open source projects.
Open on GitHub → Explain another repo

Generated 2026-05-18 · Model: sonnet-4-6 · Verify against the repo before relying on details.