// Review C++ code against Google C++ Style Guide. Use when reviewing C++ code, pull requests, or when asked to check code style compliance.
Create and push a new semver release tag. Asks for release type (patch/minor/major), validates commit exists on remote, bumps version, and pushes the tag.
Generate C++ header files following Google Style Guide. Use when creating new header files or asking for a header template.
Check C++ naming conventions against Google Style Guide. Use when checking if names follow conventions or when renaming identifiers.
Google C++ Style Guide rules for writing clean, maintainable C++ code. Use when writing C++, reviewing code, discussing naming conventions, formatting, class design, or any C++ best practices. Covers headers, scoping, classes, functions, naming, comments, and formatting.
| name | cpp-review |
| description | Review C++ code against Google C++ Style Guide. Use when reviewing C++ code, pull requests, or when asked to check code style compliance. |
Review C++ code for compliance with the Google C++ Style Guide.
PascalCasePascalCase (accessors use snake_case)snake_casemember_kPascalCaseUPPER_CASE with project prefix#define guard: PROJECT_PATH_FILE_H_explicitprivateoverride/final for virtual overridesnullptr (not NULL or 0)auto appropriately (not excessively)unique_ptr, shared_ptr)Use severity levels:
š“ **MUST FIX**: Missing `explicit` on single-argument constructor
Line 45: `Foo(int value)` should be `explicit Foo(int value)` to prevent
implicit conversions.
š” **SHOULD FIX**: Function too long
Lines 78-145: `ProcessData()` is 67 lines. Consider breaking into smaller
functions for readability and testability.
š¢ **CONSIDER**: Use structured bindings
Line 23: `auto [iter, success] = map.insert({key, value});` would be clearer
than separate `.first` and `.second` access.