openharmonyinsight/oh-graphic-gitcode-pr-creator
skills/oh-graphic-gitcode-pr-creator/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add openharmonyinsight/openharmony-skills oh-graphic-gitcode-pr-creatorInstall 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 29, 2026, 6:33 AM124.0s1 file scanned
SKILL.md
- name:
- oh-graphic-gitcode-pr-creator
- description:
- 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.
OpenHarmony Graphic Gitcode PR Creator
Quick Start
Create a Gitcode PR by following these steps:
- Check git status - Verify modified files
- Commit changes - Add Signed-off-by to commit message
- Push to remote - Push branch to origin
- Create Issue - Create related issue
- Create PR - Use PR template from
.gitcode/PULL_REQUEST_TEMPLATE.zh-CN.md
Workflow
1. Check Git Status
git status
git diff <file>
2. Commit Changes
Get user config and create commit with Signed-off-by:
git config user.name
git config user.email
git add <files>
git commit -m "<message>\n\nSigned-off-by: <name> <<email>>"
3. Push to Remote
git push origin <branch-name>
Note: You need to ask the user for the target branch name before creating the PR. Common options:
master(default for most cases)OpenHarmony-6.1-Release(for 6.1 release branch)
4. Create Issue
Use gitcode_create_issue to create issue with:
- Title: PR title
- Body: Description of changes
5. Create PR
Read PR template from .gitcode/PULL_REQUEST_TEMPLATE.zh-CN.md and fill in:
- Description: Summary of changes
- Issue number: Link to created issue
- Test & Result: Test information
- CodeCheck: Fill all self-check results with "Pass"
- L0新增用例自检结果: Check appropriate box
Use gitcode_create_pull_request with formatted body.
CodeCheck Template
When filling CodeCheck table, ensure all rows have "Pass" in the result column:
| 类型 | 自检项 | 自检结果 | |-------|---------|-----------| | 多线程 | ... | Pass | | 内存操作 | ... | Pass | | 外部输入 | ... | Pass | | 敏感信息 | ... | Pass | | 数学运算 | ... | Pass | | 初始化 | ... | Pass | | 权限管理 | ... | Pass |
Common Patterns
Test Optimization PRs
For test file optimizations:
- Description: "Optimize <test_file> - remove redundant code and improve coverage"
- CodeCheck: All Pass (test code doesn't typically trigger security checks)
- L0用例: Check "是，有新增L0用例，且完成自检"
Bug Fix PRs
For bug fixes:
- Description: "Fix <bug_description> in <file>"
- Test & Result: Describe test scenario and expected behavior
- CodeCheck: All Pass
Important Notes
- Always use the Chinese PR template for OpenHarmony projects
- Ensure branch name is descriptive
- Link PR to issue for traceability
- Force push with
--forcewhen amending commits
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