tdd

8

openharmony

This skill should be used when writing unit tests, TDD test cases, test coverage analysis, or test-driven development for NG component Pattern methods (e.g., OnModifyDone, OnDirtyLayoutWrapperSwap). Covers test principles, templates, common pitfalls, branch coverage, API verification, state reset, and mandatory self-checklist for ace_engine testing.

openharmony-build

8

openharmony

Use this skill when the user asks to "compile OpenHarmony", "build OpenHarmony", "compile the full code", "execute build", "compile OpenHarmony code", "fast build", "skip gn build", "fast-build", "compile tests", "compile test cases", "build ace_engine_test", "compile SDK", "build SDK", "compile ohos-sdk", "compile test list", "build test list", "build tests from a list", "build specified tests", "build coverage version", "build coverage", or otherwise mentions building the full OpenHarmony system, fast rebuilds, test compilation, SDK compilation, building tests from a target list, or building tests with code coverage enabled. It handles the complete build process including build execution, success verification, and failure log analysis, with primary focus on out/{product}/build.log.

diff-apply

8

openharmony

Apply generated .diff or .patch files to the ace_engine repository (TypeScript/C++ hybrid codebase) with intelligent conflict resolution. Use this when applying patches to ace_engine code to resolve merge conflicts while preserving original logic, or to validate changes by compiling after patching. The target repository path is ROOT/code/foundation/arkui/ace_engine in a repo-manifest project.

task-progress

uboy

Interactively produce a high-quality English progress comment for tracker tasks, with ArkUI/OpenHarmony risk coverage and optional mapping to structured task descriptions (expected outcome, scope, acceptance criteria).

OpenHarmony Task Specifier

uboy

Help developers write one high-quality OpenHarmony task description by asking guiding questions and producing a clear final draft with expected outcome, scope, verification, and domain-specific risks.