Loading...
Loading...
Found 23 Skills
Automate Gitcode Pull Request creation workflow for OpenHarmony graphic subsystem including code commit, issue creation, and PR submission with proper template formatting. Use when user needs to create a PR for the Gitcode platform, especially for OpenHarmony graphic projects that require specific PR templates with CodeCheck tables and Signed-off-by tags.
Use when reviewing OpenHarmony C++ system service code for security vulnerabilities, particularly IPC handlers, multithreaded components, or code handling sensitive user data
OpenHarmony Distributed Soft Bus Code Security Review Expert - Comprehensive inspection of C/C++ code against secure coding standards and logging specifications. Covers over 40 security rules, including key areas such as pointer safety, memory management, lock management, and sensitive information protection. Provides cross-file call analysis and control flow analysis, generating detailed code review reports. Only triggered when user input contains "软总线安全卫士" (Soft Bus Security Guard). ⚠️ Important: This skill is a read-only review tool and does not modify source files.
A dedicated skill for security code review of OpenHarmony distributed systems. Triggered when users make requests such as "review code security implementation", "code security audit", "security code review" or similar distributed system code security review requests. This skill provides detailed review guidance for 18 security design rules for OpenHarmony distributed services, covering security areas such as authorization control, state machines, data transmission, permission management, and trusted relationships. Using this skill, you can conduct specialized security reviews for OpenHarmony distributed systems based on general cybersecurity rules.
Use when the user wants to download OpenHarmony daily build images or flash them to a real device (DAYU200/RK3568 or others). Triggers on daily build, DAYU200, RK3568, flashing, burning, hdc reboot, upgrading firmware.
Develop, sign, deploy, and verify standalone OpenHarmony apps whose APIs or permissions may require `hos_system_app`, an elevated APL, ACL/provisioning, or a Full SDK system API. Use for privileged inspection or control of other apps or protected device state and for `Not System App` failures, then verify requirements against the exact SDK metadata. For public ordinary-app capabilities use `ohos-app-dev`; for OHOS source-tree components use `ohos-system-dev`.
Use when measuring the RAM/ROM impact of changes to the OpenHarmony Multimodal Input (MMI) subsystem on DAYU200 (RK3568). Covers ROM measurement through readelf section analysis and file-size comparison, RAM measurement through /proc/PID/smaps, smaps_rollup, hidumper --mem, and a baseline/current .so swap methodology, and code-level theoretical analysis of heap-allocated data structures.
Use when testing OpenHarmony input features that depend on window/display state without running real WMS/DMS. Builds requested simulation scenarios from display groups, users, main/extended/mirror displays, per-display focus windows, z-order window stacks, hot areas, dynamic focus switching, pointer style, capture mode, scroll wheel, and device binding.
Provides UT-based code coverage report generation for OpenHarmony C/C++, supporting both full and incremental coverage analysis, and requires a test device to be connected through hdc. Use when: (1) the user requests full code coverage for a subsystem, part, module, test suite, or test case; if a report path is provided, parse it as the --output path; (2) the user requests incremental code coverage for a part, module, test suite, or test case, requiring git diff files; if a report path is provided, parse it as the --output path. Note: incremental coverage does not support the subsystem level. Activate when an OpenHarmony device must be connected to execute tests.
Documentation knowledge correctness validation. Inspect whether the technical descriptions in OpenHarmony API documentation are consistent with authoritative standards and specifications (W3C, CSS, etc.), mathematical definitions, or industry facts. When a knowledge issue is found, further compare it against the implementation code to distinguish a "documentation error," a "code implementation error," or an inconsistency across all three. Trigger phrases: documentation description validation, documentation knowledge correctness, whether a description is accurate, parameter description validation, documentation correction, and documentation-to-code comparison.
Develop, build, deploy, and validate ordinary sandboxed HarmonyOS applications on a connected device. Use for the inner dev loop on an existing project when its APIs and permissions are available to ordinary apps. If they may require `hos_system_app`, an elevated APL, ACL/provisioning, or a Full SDK system API, use `ohos-system-app-dev` for privilege preflight.