claude

google-engineering

Google's engineering practices as operational skills: style guides for ten languages, the CL author and reviewer guides, the testing discipline from Software Engineering at Google, and commit, branch and release mechanics. Carries the unabridged primary sources offline. Reference text is reproduced under CC BY 3.0; see NOTICE.

1 on GitHubby Daniel Kosukhinv1.0.0MITupdated 1 month ago
/

Plugin google-engineering from marketplace fishnos in fishnos/claude-config. Commands read from the repo's manifest — 1 month ago.

What it installs

Skills (5)

  • git-workflow

    Industry-standard version control — atomic commits, commit message anatomy, Conventional Commits, git trailers, branching models, rebase vs merge, PR hygiene, SemVer, changelogs, tags, signing, and history-recovery. Use before writing any commit message, when splitting work into commits, when choosi

  • google-cl-author

    Author changes the way Google expects them — one self-contained change per commit/PR, tests in the same change, a description that says what and why, and collaborative responses to review feedback. Use when planning how to split work into commits or PRs, writing a commit message or PR description, d

  • google-code-review

    Review code the way Google reviews a CL — design first, then functionality, complexity, tests, naming, comments, style, consistency, documentation, every line. Use whenever reviewing a diff, PR, branch, or file someone (including you) just wrote; whenever asked to "review", "check", "look over", "cr

  • google-style

    Google's language style guides — TypeScript, JavaScript, HTML/CSS, Python, Shell, Go, Java, C++, C#, Objective-C — as the authority on formatting, naming, comments, and language-feature use. Use before writing or editing code in any of these languages, when reviewing style in a diff, when naming thi

  • google-testing

    Google's testing discipline — test sizes and scopes, the 80/15/5 mix, testing behaviors not methods, DAMP over DRY, preferring real implementations over mocks, and avoiding brittle change-detector tests. Use when writing or reviewing any test, deciding what to test or at what level, choosing between

View source on GitHub

More from fishnos/claude-config

All 3 plugins →

Make a repository legible to an agent: build a queryable knowledge graph of the codebase, audit what agent infrastructure the repository is missing, declare its scheduled cloud agents as committed files, and fetch current library documentation instead of answering from training data.

4 skills

1

Frontend work held to a visible bar: interface design and critique, React Testing Library discipline with MSW at the network boundary, and a structured discovery pass that settles UX before any code is written.

3 skills

1

Maintain google-engineering?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex plugins3 plugins