skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
openharmonyinsight/openharmony-skills139 installs

openharmony-cpp

Expert coding guide for OpenHarmony C++ development. Use this skill when writing, refactoring, or reviewing C++ code for OpenHarmony projects. It enforces strict project-specific conventions (naming, formatting, headers) and critical security requirements (input validation, memory safety).

How do I install this agent skill?

npx skills add https://github.com/openharmonyinsight/openharmony-skills --skill openharmony-cpp
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    This skill is a coding guide for OpenHarmony C++ development, providing naming, formatting, and secure coding standards. It consists entirely of documentation and contains no executable scripts, tools, or external dependencies.

  • Socketpass

    No alerts

  • Snykpass

    Risk: LOW · No issues

  • Runlayerwarn

    5/5 files flagged

  • ZeroLeakspass

    Score: 93/100 · 2 sections analyzed

What does this agent skill do?

OpenHarmony C++ Coding Skills

Core Mandates (Common Pitfalls)

These rules are strictly enforced in OpenHarmony and often differ from general C++ projects.

1. Strict Naming & Formatting

  • Extensions: Always use .cpp and .h.
  • Files: Filenames must match class names (Unix-like, e.g., my_class.cpp).
  • Variables: Global vars must start with g_ (e.g., g_config). Class members must end with _ (e.g., value_).
  • Braces: K&R Style is mandatory (opening brace on the same line).
  • Details: See naming_formatting.md.

2. Header Management

  • Guards: Use #ifndef guards. #pragma once is FORBIDDEN.
  • Includes: Prefer #include over forward declarations to prevent hidden dependencies.
  • Details: See headers_scopes.md.

3. Critical Security Requirements

  • Input Validation: All external data must be validated before use (indices, sizes, loops).
  • Memory Safety: Pointers must be set to nullptr immediately after deletion.
  • Bitwise: Only on unsigned types.
  • Details: See secure_coding.md.

Usage Guide

When to use

  • New Code: Generating new classes or modules.
  • Refactoring: Cleaning up legacy code.
  • Review: Checking code against OpenHarmony standards.

Reference Map

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/openharmonyinsight/openharmony-skills/openharmony-cpp">View openharmony-cpp on skillZs</a>