playbooks

home / skills / openharmonyinsight / openharmony-skills / oh-graphic-gitcode-pr-creator

oh-graphic-gitcode-pr-creator skill

/skills/oh-graphic-gitcode-pr-creator

This skill automates OpenHarmony graphic Gitcode PR creation by guiding status, commits with Signed-off-by, issue and PR template generation.

npx playbooks add skill openharmonyinsight/openharmony-skills --skill oh-graphic-gitcode-pr-creator

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
2.8 KB
---
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:

1. **Check git status** - Verify modified files
2. **Commit changes** - Add Signed-off-by to commit message
3. **Push to remote** - Push branch to origin
4. **Create Issue** - Create related issue
5. **Create PR** - Use PR template from `.gitcode/PULL_REQUEST_TEMPLATE.zh-CN.md`

## Workflow

### 1. Check Git Status

```bash
git status
git diff <file>
```

### 2. Commit Changes

Get user config and create commit with Signed-off-by:

```bash
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

```bash
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 `--force` when amending commits

Overview

This skill automates Gitcode pull request creation for the OpenHarmony graphic subsystem, handling commit creation, issue linking, and PR submission using the project PR template. It ensures commits include Signed-off-by lines, fills the CodeCheck table with required results, and formats the PR body to meet OpenHarmony conventions. The workflow reduces manual steps and enforces traceability between issues and PRs.

How this skill works

The skill inspects the local git workspace, stages and commits changes with user name and email, and prompts for the target branch to push. It can create a linked issue via the Gitcode API, reads the project PR template from the repository, fills required sections (description, test results, CodeCheck table, and Signed-off-by), and submits the pull request to Gitcode. It also supports amend-and-force-push workflows when commit messages need adjustment.

When to use it

  • Creating a PR for OpenHarmony graphic subsystem changes that must follow the project PR template.
  • When you need a PR with a linked issue and properly formatted Signed-off-by commit messages.
  • Submitting bug fixes, test optimizations, or new L0 test cases to the Gitcode platform.
  • Preparing PRs that require a completed CodeCheck table and explicit test results.

Best practices

  • Run git status and review diffs before staging to avoid unintended files in the commit.
  • Include a clear, descriptive branch name and prompt the user for the target branch.
  • Always append Signed-off-by with git config user.name and user.email in the commit message.
  • Fill every CodeCheck row with explicit results (use "Pass" if checks were performed).
  • Link the PR to a created issue for traceability and include test steps and expected outcomes.

Example use cases

  • Submit a bug fix: commit the fix, create an issue describing the bug, and open a PR referencing the issue with CodeCheck filled.
  • Optimize test files: create a PR that documents test improvements, marks L0 additions, and sets all CodeCheck results to Pass.
  • Add a new graphic feature: create a descriptive PR, include test & result section, and ensure Signed-off-by is present.
  • Amend commit messages: update commit to include Signed-off-by, force-push the branch, and update the PR body accordingly.

FAQ

Which PR template is used?

The skill reads the OpenHarmony PR template file from .gitcode/PULL_REQUEST_TEMPLATE.zh-CN.md and fills required sections.

What should I put in the CodeCheck table?

Provide explicit self-check results for each row; for standard passes use "Pass" and describe any deviations in the PR body.