gitcode-pr

Name: gitcode-pr
Availability: InStock
Author: openharmonyinsight

Create GitCode issues, branches, and cross-fork pull requests with templated bodies.

31|6|Updated Jan 29, 2026

Search Tags:#pull request #pr template #conventional commits #api orchestration #gitcode #issue workflow #cross-repo automation

Ready to run

npx skills add https://github.com/openharmonyinsight/openharmony-skills --skill gitcode-pr

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gitcode-pr
Source: https://github.com/openharmonyinsight/openharmony-skills/tree/main/workflows/arkweb/.aceharness/skills/gitcode-pr
Command: npx skills add https://github.com/openharmonyinsight/openharmony-skills --skill gitcode-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the error-prone, repetitive work of manually coordinating the Issue → branch → commit → PR workflow across GitCode repositories, while enforcing consistent templates and correct cross-fork PR direction.

Core Features & Use Cases

Multi-repo Issue and PR coordination: Creates and links Issues according to engine/framework layer rules for ArkWeb-related repositories.
Template-driven PR bodies: Reads the target repository’s PR template (with fallback) and fills it with the required content plus a design-document index.
Deterministic GitCode API execution: Uses Python 3 urllib with token-based authentication to call GitCode API endpoints for issues, PRs, and merges.

Quick Start

Run the gitcode-pr skill in subagent mode for your ArkWeb PR task and provide the file list plus issue/feature names so it can create the Issue, push the docs branch to your fork, and open the cross-repo PR.

Frequently Asked Questions about gitcode-pr

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

FAQPage Schema

How do I automate creating GitCode issues and cross-fork pull requests?▼

You can automate creating GitCode issues and cross-fork pull requests by using an Issue-first workflow that pushes a properly named branch and opens PRs with correctly templated bodies. This removes the repetitive work of manually coordinating the Issue, branch, commit, and PR workflow across GitCode repositories.

How do I ensure my pull request template is filled correctly for ArkWeb repositories?▼

To ensure your pull request template is filled correctly, the workflow reads the target repository’s PR template, applies a fallback if needed, and fills it with the required content plus a design-document index. This enforces consistent templates for ArkWeb multi-repository submission workflows.

Can I execute a PR merge using the GitCode API with token authentication?▼

Yes, you can execute optional PR merges using the GitCode API with token authentication. The process uses Python 3 urllib with PRIVATE-TOKEN authentication to call GitCode API endpoints for deterministic issue, PR, and merge execution.

What is the best way to handle duplicate PR branches and backend timeouts on GitCode?▼

The best way to handle duplicate PR branches and backend timeouts on GitCode is to use a deterministic API execution flow that manages common GitCode API errors. This approach handles backend timeouts and duplicate branch errors during cross-fork PR creation.

Do I need Python 3 to coordinate multi-repo PR workflows for ArkWeb?▼

Yes, you need Python 3 to coordinate multi-repo PR workflows for ArkWeb. The workflow requires Python 3 urllib-based GitCode API calls using PRIVATE-TOKEN authentication to orchestrate repositories like chromium_src, web_webview, and arkui_ace_engine.

Why does my cross-repo pull request direction fail during multi-repository coordination?▼

Cross-repo pull request direction fails when manual coordination does not enforce the correct cross-fork PR direction. Automating the Issue-first flow with deterministic GitCode API execution ensures the correct cross-fork PR direction for engine and framework layer rules.