Skip to content
TrustedSkillsbeta
Back to all skills

Cpp Coding Standards

Checked
affaan-m·vlatest·backend·MIT

Enforces consistent C++ coding practices by suggesting improvements and identifying deviations from established standards, boosting code quality & maintainability.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add affaan-m/ecc --skill cpp-coding-standards -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

affaan-m

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned affaan-m/everything-claude-code at d3b8a3e908.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
d3b8a3e908
Manifest
skills/cpp-coding-standards/SKILL.md
Scanned
3 files, 1,419 lines
Copies in repo
3 — all of them scanned
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The cpp-coding-standards skill helps enforce and maintain consistent coding practices in C++ projects. It provides guidance on naming conventions, code structure, documentation standards, and best practices for writing clean, readable, and efficient C++ code.

When to use it

  • When starting a new C++ project and establishing team-wide coding guidelines.
  • When reviewing or refactoring existing C++ code to ensure compliance with industry-standard practices.
  • When preparing documentation or training materials for developers working on C++ projects.

Key capabilities

  • Enforces naming conventions for variables, functions, and classes.
  • Provides formatting rules for code structure and indentation.
  • Recommends best practices for memory management and error handling.
  • Suggests documentation standards for comments and API design.

Example prompts

  • "What are the recommended naming conventions for C++ functions?"
  • "How should I format my C++ header files according to industry standards?"
  • "Can you review this C++ code snippet and suggest improvements based on best practices?"

Tips & gotchas

  • Ensure that your team agrees on which coding standard (e.g., Google, LLVM, Microsoft) to follow for consistency.
  • Some tools may require integration with linters or formatters like ClangFormat or CppCheck for full enforcement of standards.