openharmony-cpp

What problem does it solve?

OpenHarmony C++ projects often suffer from inconsistent style, fragile headers, and avoidable security bugs when code is written without strict project conventions.

Core Features & Use Cases

• Strict OpenHarmony C++ conventions: Enforces naming/formatting rules such as K&R braces, file/class alignment, and global/member variable prefixes.
• Safe header management: Requires conventional include guards and discourages #pragma once, forward-declaration hiding, and header pollution.
• Critical security requirements: Mandates input validation, integer safety rules, and memory-safety practices like nulling pointers after deletion.
• Class/function design quality: Guides modern C++ usage (e.g., explicit, nullptr, override), constructor/destructor rules, and reasonable function size/parameter limits.
• Use case: When introducing a new OpenHarmony module or refactoring legacy code, this skill helps ensure the implementation matches platform expectations and reduces security review risk.

Quick Start

Ask the AI to review your OpenHarmony C++ header and source files against naming, header-guard, include, and secure-coding requirements, and report every violation found.