oh-pr-workflow

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

31|6|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/openharmonyinsight/openharmony-skills --skill oh-pr-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: oh-pr-workflow
Source: https://github.com/openharmonyinsight/openharmony-skills/tree/main/skills/oh-pr-workflow
Command: npx skills add https://github.com/openharmonyinsight/openharmony-skills --skill oh-pr-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill removes the repetitive effort of managing the full OpenHarmony PR lifecycle on GitCode, including standardized commits, Issue/PR creation, gate/codecheck defect fixing, and review comment remediation.

Core Features & Use Cases

  • Standardized PR lifecycle on GitCode: creates DCO-signed commit messages, links/creates Issues, pushes to forks, and opens upstream PRs with CI trigger comments.
  • Gate (codecheck) defect auto-fixing: fetches failed gate defects from DCP using PR gate comment identifiers and applies best-effort fixes for known rules.
  • PR code review assistance with diff-aware mapping: pulls exact PR commits/files, prepares local review branches, presents review findings, and can auto-apply fixes for unresolved line-level review comments.
  • Use Case: When a PR fails the “代码门禁未通过” gate, fetch the defect list, auto-fix formatting/naming/nullptr issues where supported, squash into the original commit, and re-trigger build.

Quick Start

Run: /oh-pr-workflow 创建PR

Frequently Asked Questions about oh-pr-workflow

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

FAQPage Schema
How do I automate OpenHarmony pull request creation on GitCode?

Automate OpenHarmony pull request creation by using configured Git remotes to push to forks, generate DCO-signed commit messages, link Issues, and open upstream PRs with automated CI trigger comments.

What is the best way to fix failing codecheck gate defects in an OpenHarmony CI pipeline?

Fix failing codecheck gate defects by fetching the defect list from DCP using PR gate comment identifiers and applying best-effort automated fixes for known formatting, naming, and nullptr rules before squashing and re-triggering.

How do I resolve unresolved line-level review comments on a GitCode pull request?

Resolve unresolved line-level review comments by pulling exact PR commits and files, preparing a local review branch, and auto-applying fixes mapped directly to the diff-aware review findings.

Do I need a specific Git remote setup to automate OpenHarmony PR workflows?

Automating OpenHarmony PR workflows requires a configured GitCode token and both upstream and fork Git remotes to drive deterministic API and repository operations across multiple agent environments.

Can I squash auto-fixed gate defects into my original commit before re-triggering a build?

Squash auto-fixed gate defects into the original commit after applying best-effort fixes for supported codecheck rules, enabling a clean history before re-triggering the CI build.