بنقرة واحدة
growingio-sdk-harmonyos
يحتوي growingio-sdk-harmonyos على 16 من skills المجمعة من growingio، مع تغطية مهنية على مستوى المستودع وصفحات skill داخل الموقع.
Skills في هذا المستودع
Use when a feature, bugfix, or refactoring step is completed and needs review, or before merging to main, or when user says "review", "审查", "帮我看看代码"
Use when receiving an ambiguous feature request, when scope is unclear, or before writing any plan
Use after verification-before-completion passes and code review is clean, to close out the development branch
Use when executing git commit, creating or naming branches, writing PR titles/descriptions, or asking about commit message format, branch naming, or version numbering in this project
Use when writing or reviewing .ets/.ts files in this project, or when seeing any, unknown, obj['key'] index access, destructuring assignment, var declarations,
Use when user asks to create a version release ticket, says "帮我建个发版任务", "建个 Jira", "创建发版单", or needs to track an SDK release in Jira
Use when user mentions "发布 SDK"、"ohpm 发布"、"打包发布"、"上传 har"、"publish"、"发版"、"release"、"发布" or "上传" in the context of this SDK
Use after writing a plan document in docs/plans/, before requesting user confirmation
Use when receiving feedback from code-reviewer subagent or human reviewer
Use when executing an implementation plan with 3+ independent tasks in the current session
Use when facing ArkTS compile errors, hvigor build failures, hypium test failures, event pipeline bugs, network issues, SDK crashes, or any technical problem where a first attempt didn't work or the cause is unclear
Use when implementing or modifying core SDK paths (event pipeline, storage, network, session management)
Use when starting any interaction as the GrowingIO HarmonyOS SDK engineer main controller agent
Use before claiming work is complete, fixed, or ready to review
Use when Planning Gate triggers (affected files ≥3 or public API change) and an implementation plan is needed
Use when creating a new skill, editing an existing skill, or verifying a skill works before deployment