agentleFS
testdino-hqtestdino-hq/google-styleguides-skills/cpp/SKILL.md

cpp

Skill15 starsChanged 9 months agoMITView on GitHub

Google's official C++ style guide. Covers headers, naming conventions, formatting, classes, memory management, RAII, smart pointers, and modern C++ features.

7 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use kotlin.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • margeloSkill

    kotlin

    Design, implement, and review Kotlin and Android APIs. Use when working on .kt files, Kotlin nullability, sealed classes/interfaces, coroutines, Android threading, Java interop, or Kotlin-backed React Native Nitro Module implementations.

    Also in 3 projects that use this

The file

Files
SKILL.md

Google C++ Style Guide

Official Google C++ coding standards for consistent, maintainable code.

Golden Rules

  1. Target C++20 — avoid non-standard extensions
  2. 80-character line limit — for readability
  3. 2-space indentation — no tabs
  4. Use const liberally — for correctness and thread safety
  5. Avoid exceptions — Google code doesn't use C++ exceptions
  6. Smart pointers for ownership — std::unique_ptr and std::shared_ptr
  7. Header guards — use PROJECT_PATH_FILE_H_ format

Quick Reference

Naming Conventions

ElementConventionExample
Filessnake_caseurl_table.cc, url_table.h
Classes/StructsUpperCamelCaseUserService
FunctionsUpperCamelCaseGetUserById
Variablessnake_caseuser_count
ConstantskUpperCamelCasekMaxRetries
Class memberssnake_case_user_name_ (trailing _)
MacrosUPPER_SNAKE_CASEMAX_BUFFER_SIZE

Headers

// ✓ CORRECT - self-contained header with guard
#ifndef FOO_BAR_BAZ_H_
#define FOO_BAR_BAZ_H_

#include <string>
#include "base/basictypes.h"

class Baz {
 public:
  void DoSomething();
};

#endif  // FOO_BAR_BAZ_H_

Include order: related header → C system → C++ stdlib → other libs → your headers.

Classes

// ✓ CORRECT
class MyClass {
 public:
  explicit MyClass(int value);  // explicit for single-arg ctors
  ~MyClass();

  void DoSomething();
  int GetValue() const { return value_; }

 private:
  int value_;
  std::string name_;
};

Smart Pointers

// ✓ CORRECT - unique_ptr for exclusive ownership
std::unique_ptr<Foo> FooFactory();
void FooConsumer(std::unique_ptr<Foo> ptr);

// ✓ CORRECT - shared_ptr for shared ownership
std::shared_ptr<const Foo> immutable_foo;

// ✗ INCORRECT - avoid raw new/delete
Foo* foo = new Foo();  // avoid
delete foo;            // avoid

Modern C++ Features

// ✓ CORRECT - use auto for complex types
auto it = my_map.find(key);
auto widget = std::make_unique<Widget>(arg1, arg2);

// ✓ CORRECT - range-based for loops
for (const auto& item : container) {
  Process(item);
}

// ✓ CORRECT - nullptr, not NULL
Foo* ptr = nullptr;

// ✓ CORRECT - constexpr for compile-time constants
constexpr int kArraySize = 100;

Functions

// ✓ CORRECT - return type on same line
ReturnType ClassName::FunctionName(Type par_name1, Type par_name2) {
  DoSomething();
  return result;
}

// ✓ CORRECT - wrap long parameter lists (4-space indent)
ReturnType LongClassName::ReallyLongFunctionName(
    Type par_name1,
    Type par_name2,
    Type par_name3) {
  DoSomething();
}

Formatting

// ✓ CORRECT - braces and spacing
if (condition) {
  DoSomething();
} else {
  DoSomethingElse();
}

// ✓ CORRECT - pointer/reference alignment (attached to type)
char* c;
const std::string& str;

Common Mistakes

MistakeCorrect Approach
Using exceptionsUse error codes or absl::Status
Bare new/deleteUse smart pointers (unique_ptr)
NULL or 0 for nullUse nullptr
C-style castsUse C++ casts (static_cast, etc.)
using namespace stdNever in headers; avoid in .cc
Mutable global variablesUse singletons or dependency injection
Missing explicitMark single-arg constructors explicit

When to Use This Guide

  • Writing new C++ code
  • Refactoring existing C++
  • Code reviews
  • Setting up clang-format rules
  • Onboarding new team members

Install

npx skills add testdino-hq/google-styleguides-skills/cpp

Full Guide

See cpp.md for complete details, examples, and edge cases.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.