openharmonyinsight/audio_pr_create
skills/audio_pr_create/SKILL.md
使用oh-gc CLI管理GitCode仓库时使用 — 包括认证、issues、PRs、评审人、测试人员、标签、发布和仓库配置。当用户想要提交代码，创建ISSUE，创建PR,更新PR等涉及gitcode网页的操作时使用该技能。
$ install --global
skillsauthnpx skillsauth add openharmonyinsight/openharmony-skills audio_pr_createInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 22, 2026, 5:33 AM119.4s9 files scanned
SKILL.md
- name:
- audio_pr_create
- description:
- 使用oh-gc CLI管理GitCode仓库时使用 — 包括认证、issues、PRs、评审人、测试人员、标签、发布和仓库配置。当用户想要提交代码，创建ISSUE，创建PR,更新PR等涉及gitcode网页的操作时使用该技能。
初始化
- 查看当前是否配置令牌，如果没有配置，用
./assets/config.json中的'username'和'token'进行git的配置
git config --global credential.helper store
初始化仓库
- 采用
git remote -v查看当前远端仓库是否存在，远端仓库一般下列形式：
upstream https://gitcode.com/openharmony/multimedia_audio_framework (fetch)
upstream https://gitcode.com/openharmony/multimedia_audio_framework (push)
- 查看fork仓库是否添加，fork仓库格式为: "https://gitcode.com/{username}/{repo}.git"其中，{username}和{repo}为
./assets/config.json中的'username'和'token'，fork仓库一般命名为origin， 如果没有，使用git remote add加上
初始化oh-gc CLI
- 参考
./references/Readme.md进行oh-gc的初始化，其中登录使用的token采用./assets/config.json的token
提交注意事项
- 判断当前代码是否有更新
- 查看一下当前用户是否已经git commit过，如果用户已经commit，则push到远端fork仓库，否则，帮助用户进行commit操作，注意！！
git commit时必须要加上-s，-m的信息中添加"Co-Authored-By: Agent"，提交后进行push到origin的fork仓库 - 查看当前是否已经存在相关PR，如果当前修改只是修改上一笔PR的代码，则直接采用
git commit --amend后进行push注意添加 -f 不需要重新创建PR，直接结束当前技能。否则进行push，并开始下面的PR的创建 - 遵循创建流程，先创建ISSURE然后将ISSUE绑定到PR之中
创建流程
Step1.创建ISSUE
// title根据当此任务以及修改确认
// body根据指定的labels选择`assets/ISSUE_TEMPLATE`中的指定模板，必须选择模板，不能自己生成，body中的内容需要进行填充，模板中的版本选择master
// labels需要和模板匹配
// repo为 owner/repo
oh-gc issue:create --repo openharmony/multimedia_audio_framework --title "test cli" --body "test cli" --labels "bug"
如果成功创建则获得返回："https://gitcode.com/openharmony/multimedia_audio_framework/issues/11908" 记录其中的"issue_id"为11908
Step2.创建PR
参数配置
- title需要根据当此任务以及修改确认
- head为当前提交分支
- body选择
assets/PR_TEMPLATE/PULL_REQUEST_TEMPLATE.zh-CN.md并根据内容将模板中的自检结果更新,其中IssueNo字段应该填写创建ISSUE中返回的ISSUE url. **通用规范自检：**字段必须根据本次修改进行填写自检结果，|Y/N/NA|必须选择其中一个进行填写 - repo为 owner/repo
- base一般为 master
oh-gc pr:create --repo openharmony/multimedia_audio_framework --head feature --base master --title "PR标题" --body body
如果创建成功则返回："Created PR #14486: PR标题" 失败，则去查询pr中是否存在已经创建好的，如果存在则返回，如果不存在则直接返回失败原因告知用户，结束流程.
Step3.开始构建
成功创建PR后，询问用户是否需要开始构建？ 用户否认，则退出流程。 用户需要，则等待PR完全初始化后,等30s,帮助用户开始构建
oh-gc pr:comment 14486 --body "start build"
如果失败，进行重试，重试3次之后如果依旧失败，则告知用户失败原因并退出。
Related Skills
openharmonyinsight/skills/ohos-req-value-decision
testing
VerifiedTrustedCommunity
--- name: ohos-req-value-decision description: Use after review meeting to record decision and route to next step. Triggers: 评审决策纪要, 评审结论回流, value decision, 评审接纳, 评审不接纳, 评审退回, 下次重新上会. Do NOT use for feature baseline (ohos-req-feature-baseline), review gate checks (ohos-req-review-gate), or IR generation (ohos-req-feature-to-ir). metadata: author: openharmony scope: common stage: requirements capability: value-decision version: 0.3.0 status: draft tags: - sdd - requirements
30SKILL.mdUpdated Jul 22, 2026
openharmonyinsight/ohos-req-review-ppt-gen
development
VerifiedTrustedCommunity
Use when converting an OpenHarmony requirement document, spec, or design proposal into an OpenHarmony review slide deck (需求评审 / 需求变更评审 / 设计评审 PPTX) — produces the fixed OpenHarmony-branded review-deck structure (OH logo on every page) with architecture/flow diagrams and field tables. Triggers on "需求评审PPT", "需求变更评审", "把需求文档转成评审PPT", "spec转评审PPT", "requirement/spec to review deck". NOT for arbitrary or generic slide decks unrelated to OpenHarmony requirement/design review.
30SKILL.mdUpdated Jul 22, 2026
openharmonyinsight/ohos-req-review-gate
testing
VerifiedTrustedCommunity
Use when performing the Phase 0 Step 0.5 Review Ready Gate on a 04-feature.md, especially when the user says "evaluate gate", "review readiness", "feature ready?", "should we generate IR", or when the ohos-req-intake-orchestration main session needs a structured Ready / Conditional Ready / Not Ready judgment instead of doing the check inline. Reads 01-04, runs seven fixed checks plus a conditional-items check, and returns a machine-readable JSON summary plus a human-readable table that the main session can route on. Do NOT use for feature baseline generation (ohos-req-feature-baseline), value decision recording (ohos-req-value-decision), or IR generation (ohos-req-feature-to-ir).
30SKILL.mdUpdated Jul 22, 2026
openharmonyinsight/skills/ohos-req-requirement-intake
testing
VerifiedTrustedCommunity
--- name: ohos-req-requirement-intake description: Use when importing an OHOS requirement into Phase 0.1, especially for 01-requirement.md, requirement intake, background, user value, scenarios, scope, FR/NFR, affected modules, or priority. Triggers: 需求导入, 01-requirement, 需求基线, RR单号. Do NOT use for feasibility analysis (ohos-req-feasibility-analysis), architecture decision (ohos-req-arch-decision), or feature baseline (ohos-req-feature-baseline). metadata: author: openharmony scope: common
30SKILL.mdUpdated Jul 22, 2026