oh-graphic-gitcode-pr-creator_skill

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.