openharmony-cpp_skill

Overview

This skill is an expert coding guide for OpenHarmony C++ development. It enforces strict project conventions for naming, formatting, and header management and highlights critical security requirements such as input validation and memory safety. Use it to produce, refactor, or review C++ code that must comply with OpenHarmony standards.

How this skill works

The skill inspects C++ source and header files for adherence to OpenHarmony rules: file extensions, filename-to-class mapping, variable and member naming, and K&R brace style. It verifies header guards (no #pragma once), prefers explicit includes over forward declarations, and checks for proper input validation, pointer nullification after delete, and safe bitwise usage on unsigned types. It flags deviations and offers concrete corrective recommendations.

When to use it

• Creating new classes or modules for OpenHarmony projects.
• Refactoring legacy C++ code to conform to OpenHarmony conventions.
• Performing code reviews to enforce naming, formatting, and security rules.
• Auditing headers and include scopes to eliminate hidden dependencies.
• Verifying memory management and input validation before release.

Best practices

• Use .cpp and .h file extensions and match filenames to class names using Unix-like lowercase and underscores.
• Prefix global variables with g_ and suffix class members with _. Keep member visibility clear and prefer small, focused functions.
• Apply K&R brace style (opening brace on the same line) and respect configured line length and indentation rules.
• Always use #ifndef header guards; do not use #pragma once. Prefer explicit #include over forward declarations to avoid hidden dependencies.
• Validate all external input (sizes, indices, loop bounds) before use. Nullify pointers immediately after delete and avoid unsafe casts.
• Perform bitwise operations only on unsigned integer types. Follow secure_coding rules for prohibited functions and integer safety.

Example use cases

• Generate a new OpenHarmony-compliant class with correct file naming, header guard, and member naming.
• Refactor a legacy module: convert global and member names, apply K&R braces, and replace pragma once with header guards.
• Review a pull request to detect missing input validation or pointer nullification after deletion.
• Audit header includes to replace forward declarations with explicit includes where required.
• Fix bitwise operations that use signed types and validate loop bounds to prevent out-of-bounds access.