skills.rest
openharmonyinsight
openharmonyinsightOFFICIAL
Explore all skills by this author →
GitHub

graphic-2d-PR

Create OpenHarmony graphic_graphic_2d pull requests with DCO-signed commits and issue linking.

31|6|Updated Jan 29, 2026
Search Tags:#pull request#issue linking#openharmony#gitcode#github-style workflow#dco signed commits#graphic_2d
One-click install
npx skills add https://github.com/openharmonyinsight/openharmony-skills --skill graphic-2d-pr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: graphic-2d-PR
Source: https://github.com/openharmonyinsight/openharmony-skills/tree/main/skills/graphic-2d-PR
Command: npx skills add https://github.com/openharmonyinsight/openharmony-skills --skill graphic-2d-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the friction of creating OpenHarmony graphic_graphic_2d pull requests by guiding you through the correct sequence of branch preparation, signed commits, issue creation, PR submission, and issue-PR linking with the required base branch and conventions.

Core Features & Use Cases

  • End-to-end PR workflow: Stages changes, creates a feature branch, and produces a DCO-compliant signed commit before any network actions.
  • GitCode integration: Creates an upstream issue and then opens a PR against the correct base branch using GitCode MCP tools.
  • Auto-linking and traceability: Ensures the PR body includes the proper Closes directive so the issue links automatically, and adds a follow-up issue comment when needed.
  • Use Case: When you implement a fix or refactor in the OpenHarmony graphic_graphic_2d repository, use this Skill to reliably generate the required issue + PR pair with consistent titles and linkage.

Quick Start

Tell the AI to run the graphic-2d-PR workflow to create an upstream issue and PR for your current changes in the graphic_graphic_2d repository, linking them together automatically.

Frequently Asked Questions about graphic-2d-PR

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

FAQPage Schema
How do I create a pull request for OpenHarmony graphic_2d with an linked issue?▼

To create a linked pull request for OpenHarmony graphic_2d, you need to prepare a DCO signed commit, create an upstream issue, submit the PR, and link them using a Closes directive. This workflow ensures proper traceability and compliance.

What is the correct workflow for submitting DCO signed commits to OpenHarmony graphic_2d?▼

The DCO signed commits workflow for OpenHarmony graphic_2d involves staging changes, creating a feature branch, and producing a signed commit before executing network actions like issue creation and PR submission via GitCode MCP tools.

Do I need GitCode MCP tools to open a pull request against the graphic_2d repository?▼

Yes, you need GitCode MCP tools to execute create_issue, create_pull_request, and create_issue_comment actions. These tools handle the structured title and body formats required for master-base PRs in the graphic_2d repository.

How does issue linking work when submitting a GitCode pull request for graphic_2d?▼

Issue linking works by including a proper Closes directive in the PR body so the associated issue links automatically. A follow-up issue comment is added via GitCode tools when needed to ensure complete traceability.

Can I use a standard GitHub-style workflow for OpenHarmony graphic_2d pull requests?▼

While OpenHarmony graphic_2d uses a GitHub-style workflow, it requires specific GitCode repository targets for master-base PRs, descriptive branch naming, and DCO signed commits to meet project contribution conventions.

Why is my graphic_2d pull request missing the issue traceability link on GitCode?▼

Missing issue traceability usually occurs if the PR body lacks the proper Closes directive or if the upstream issue was not created beforehand using the GitCode MCP tools before opening the pull request.

Related Skills

Explore More Software Engineering Skills→
alexandremendoncaalvaroalexandremendoncaalvaro
728

ad-commit

Draft atomic Conventional Commits with DCO Signed-off-by sign-off.

Community
Advanced
leafcoderleafcoder
2

Gitee Workflow Automation

Automate Gitee repository tasks like issue tracking and pull requests.

Community
Intermediate
openharmonyinsightopenharmonyinsight
31

oh-pr-workflow

Automate OpenHarmony GitCode pull request workflows with commit standardization and defect fixing.

Official
Advanced
openharmonyinsightopenharmonyinsight
31

oh-graphic-gitcode-pr-creator

Automate Gitcode PR creation for OpenHarmony graphic subsystem changes.

Official
Intermediate