Summary
The review comments you would have made anyway, made first.
Naming, const, include guards and the dangling pointer are what every C++ review spends its first ten minutes on. Getting them out of the way before a human reads the diff leaves the review for the parts that need an argument.
What it is
A style and safety checker for C++ source, with the guideline material behind it readable over the same connection: naming rules, best-practice guides, standard feature docs and design pattern examples.
What you get
- Identifiers validated against naming conventions — variables, classes, functions, namespaces
- Header include guards or #pragma once checked
- Memory safety analysed for leaks, dangling pointers and unsafe patterns
- Modernisation suggestions targeting anything from C++11 through C++23
- Missing const found on member functions, parameters and variables
- Reference material addressable by URI: naming by category, best practices by topic, standard features by version, and patterns including RAII, Pimpl, Factory and Observer
- Two prompt templates — a code review with a general, performance, safety, readability or modern slant, and a refactoring guide aimed at a chosen standard
Requirements
Nothing, if you point a client at the hosted endpoint https://cpp-style-guide-mcp.fly.dev/mcp. Run it locally instead with uv and a clone, or let Smithery install it into your client.
Setup effort
One command — npx -y @smithery/cli install @SongJiangzhou/cpp_guidelines --client claude