cpp-coding-standards

Enforce C++ Core Guidelines for safe coding across codebases.

1|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/ROLLED740/vibe-clone-pro --skill cpp-coding-standards-rolled740
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cpp-coding-standards
Source: https://github.com/ROLLED740/vibe-clone-pro/tree/main/.agent/skills/cpp-coding-standards
Command: npx skills add https://github.com/ROLLED740/vibe-clone-pro --skill cpp-coding-standards-rolled740

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Modern C++ projects struggle with inconsistent coding practices, unsafe patterns, and ambiguous ownership semantics that slow maintenance and introduce bugs. This Skill codifies the C++ Core Guidelines into actionable standards to guide writing, reviewing, and refactoring code for safety and clarity.

Core Features & Use Cases

  • Clear, enforceable rules for type safety, resource management, immutability, and interface design.
  • Guidance for RAII, value semantics, smart pointers, and exception safety across templates and classes.
  • Use Case: apply these standards during new development, code reviews, or refactoring to reduce defects and improve readability.

Quick Start

Read the C++ Core Guidelines and begin applying the documented rules to your current codebase by auditing key modules and progressively updating them.

Frequently Asked Questions about cpp-coding-standards

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce modern C++ coding standards during a code review?

Enforce modern C++ coding standards by applying the C++ Core Guidelines to code reviews, checking for type safety, RAII, value semantics, and smart pointer usage to reduce defects and improve readability.

What are the C++ Core Guidelines for resource management and ownership?

The C++ Core Guidelines for resource management dictate using RAII, value semantics, and smart pointers to ensure clear ownership semantics and exception safety across templates and classes.

How do I refactor legacy C++ code for type safety and immutability?

Refactor legacy C++ code for type safety and immutability by auditing key modules and progressively updating them with enforceable rules for interface design and safe patterns.

Can I apply C++ coding standards to templates and class design?

Yes, you can apply C++ coding standards to templates and class design to ensure proper resource management, exception safety, and clear interface design across new development and refactoring.

Why does ambiguous ownership semantics introduce bugs in C++ projects?

Ambiguous ownership semantics introduce bugs in C++ projects because inconsistent coding practices and unsafe patterns slow maintenance and make resource lifecycle management unpredictable.