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

audio_pr_create

Automate GitCode issue and pull request creation with oh-gc templates.

31|6|Updated Jan 29, 2026
Search Tags:#workflow automation#issue linking#pr creation#gitcode#oh-gc#build trigger#assets templates
One-click install
npx skills add https://github.com/openharmonyinsight/openharmony-skills --skill audio-pr-create
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: audio_pr_create
Source: https://github.com/openharmonyinsight/openharmony-skills/tree/main/skills/audio_pr_create
Command: npx skills add https://github.com/openharmonyinsight/openharmony-skills --skill audio-pr-create

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

This Skill automates the repetitive GitCode workflow of creating issues and pull requests (and optionally kicking off builds) when using the oh-gc CLI, including authentication setup and safe handling of commits and existing PRs.

Core Features & Use Cases

  • Auth & repo initialization: Sets up git credential storage, validates/uses assets/config.json credentials, and prepares GitCode remotes for upstream and fork operations.
  • Issue → PR lifecycle automation: Creates an Issue from a required label-matched template, then creates a PR that links the created Issue via the PR template’s IssueNo field.
  • Commit and existing-PR handling: Detects whether the user already committed changes; uses git commit -s -m ... with a required Co-Authored-By marker for new commits, and supports git commit --amend + force-push to update the previous PR without recreating it.
  • Optional build trigger: After PR creation, asks whether to start build, waits for initialization, and posts a PR comment to start build with up to 3 retries.

Quick Start

Ask the AI to run the audio_pr_create workflow to create an issue and open a PR on OpenHarmony’s multimedia_audio_framework repo using the configured GitCode token.

Frequently Asked Questions about audio_pr_create

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

FAQPage Schema
How do I automate GitCode issue and pull request creation for OpenHarmony contributions?▼

Automating GitCode issue and PR creation involves using the oh-gc CLI to generate issues from label-matched templates and link them to new pull requests. You need a configured GitCode token in assets/config.json and consistent PR body generation referencing assets/PR_TEMPLATE.

How does issue linking work when creating a pull request on GitCode?▼

Issue linking works by generating a PR body from a template that references the newly created Issue's IssueNo. The workflow first creates an Issue from a required label-matched template, then creates a PR that links the created Issue via the PR template's IssueNo field.

Can I update an existing GitCode pull request without recreating it after making new commits?▼

Yes, you can update an existing GitCode pull request without recreating it by using git commit --amend followed by a force-push. This amend and force-push logic safely handles existing PRs while preserving the original Issue link.

Do I need to configure credentials in assets/config.json to trigger builds on GitCode?▼

Yes, triggering builds on GitCode requires configuring your GitCode token in assets/config.json for authentication. After PR creation, the workflow optionally asks to start the build, waits for initialization, and posts a PR comment to start the build with up to 3 retries.

What is the required commit format for OpenHarmony pull requests via oh-gc?▼

The required commit format for OpenHarmony pull requests uses git commit -s -m with a mandatory Co-Authored-By marker. The workflow detects whether you already committed changes and applies this specific signed-off commit format for new commits.

Why does my GitCode PR creation workflow fail when using custom issue labels?▼

GitCode PR creation fails with custom labels if there is no correct label-to-issue-template mapping in assets/ISSUE_TEMPLATE. The workflow requires a label-matched template to create the Issue before generating the PR body from assets/PR_TEMPLATE.

Related Skills

Explore More Product & Management Skills→
openharmonyinsightopenharmonyinsight
31

gitcode-cli

Manage GitCode repositories via oh-gc CLI for authentication, issues, PRs, releases, and configuration.

Official
Intermediate
mbruhlermbruhler
218

using-orchestration

Coordinate multi-agent workflows with sequential, parallel, and conditional execution.

Community
Basic
tobihagemanntobihagemann
399

contribute-turbo

Submit Turbo skill improvements to the upstream repository via fork or source modes.

Community
Intermediate
openharmonyinsightopenharmonyinsight
31

oh-graphic-gitcode-pr-creator

Automate Gitcode PR creation for OpenHarmony graphic subsystem changes.

Official
Intermediate