oh-graphic-gitcode-pr-creator

Automate Gitcode PR creation for OpenHarmony graphic subsystem changes.

31|6|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/openharmonyinsight/openharmony-skills --skill oh-graphic-gitcode-pr-creator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: oh-graphic-gitcode-pr-creator
Source: https://github.com/openharmonyinsight/openharmony-skills/tree/main/skills/oh-graphic-gitcode-pr-creator
Command: npx skills add https://github.com/openharmonyinsight/openharmony-skills --skill oh-graphic-gitcode-pr-creator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of creating OpenHarmony graphic subsystem pull requests on Gitcode with the correct commit metadata, linked issue, and properly formatted PR template (including CodeCheck “Pass” entries).

Core Features & Use Cases

  • End-to-end PR workflow: Guides you through git status verification, committing with a required Signed-off-by line, pushing to the remote branch, creating a related issue, and opening a PR.
  • Template-driven PR body generation: Ensures the PR description follows the Chinese OpenHarmony Gitcode PR template, including Issue linkage, Test & Result, and CodeCheck table filled with “Pass”.
  • Graphic-subsystem oriented usage: Tailored for OpenHarmony graphic projects where PR template formatting is mandatory for successful review.

Use Case Example: You fixed a rendering bug in the graphic subsystem and want to open a Gitcode PR that includes a linked issue and a CodeCheck section with all entries marked “Pass”.

Quick Start

Ask the AI to create a Gitcode PR for my OpenHarmony graphic changes by producing the PR title/body using the .gitcode/PULL_REQUEST_TEMPLATE.zh-CN.md template and a CodeCheck table with all results set to Pass.

Frequently Asked Questions about oh-graphic-gitcode-pr-creator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create an OpenHarmony graphic subsystem pull request on Gitcode with the correct template?

To create an OpenHarmony graphic pull request on Gitcode, you must read the PR template from .gitcode/PULL_REQUEST_TEMPLATE.zh-CN.md and format the PR body with linked issues, test results, and a CodeCheck table filled with Pass.

How do I add Signed-off-by tagging to my Gitcode commits for OpenHarmony traceability?

Adding Signed-off-by tagging to Gitcode commits requires coordinating commit preparation by appending the Signed-off-by line to your commit message before pushing to the remote branch and submitting the pull request.

What is the best way to automate the CodeCheck self-check results in an OpenHarmony PR?

Automating CodeCheck self-check results in an OpenHarmony PR involves generating a PR body from the Chinese template and ensuring every CodeCheck table row is automatically filled with the Pass entry.

Does the OpenHarmony graphic PR workflow require a linked issue before submission?

Yes, the OpenHarmony graphic PR workflow requires a linked issue before submission, coordinating issue creation and PR submission steps to ensure the template includes proper issue linkage.

Why does my Gitcode pull request fail review for the OpenHarmony graphic subsystem?

Your Gitcode pull request may fail review if the PR description does not follow the mandatory Chinese OpenHarmony template or if the CodeCheck section lacks the required Pass entries.

Can I use this workflow automation for non-graphic OpenHarmony subsystems on Gitcode?

This workflow automation is tailored for OpenHarmony graphic projects where the specific PR template formatting is mandatory, and applying it to non-graphic subsystems may not yield compliant results.