openharmony-ci

Resolve OpenHarmony PR CI job statuses and fetch failure logs from DCP events.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill resolves which OpenHarmony CI jobs failed for a given PR and retrieves the relevant logs so you can quickly identify the root cause instead of manually browsing CI systems.

Core Features & Use Cases

  • PR → DCP event resolution: Finds the newest DCP event id from openharmony_ci PR comments and uses it to query the CI event.
  • Per-job CI status summarization: Produces an overall result plus per-job results, including running/pending classification and explicit failure reasons.
  • Smart log fetching: Downloads and tails logs for failed jobs by default, with modes to fetch none/only failures/every job with artifacts.

Quick Start

Run: python3 scripts/openharmony_ci.py --pr 82764 --repo openharmony/arkui_ace_engine

Frequently Asked Questions about openharmony-ci

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

FAQPage Schema
How do I fetch failing CI logs for an OpenHarmony PR from GitCode?

To fetch failing CI logs for an OpenHarmony PR, provide the PR number and repository to resolve the latest DCP event id. The tool then summarizes failed jobs and downloads only the relevant logs for build debugging.

What is a DCP event id in OpenHarmony CI debugging?

A DCP event id in OpenHarmony CI debugging is a unique identifier for a specific continuous integration run. It is resolved from PR comments and used to query job-level outcomes, fetch artifacts, and retrieve build logs.

Can I get a summary of skipped or running CI jobs for an OpenHarmony PR?

Yes, you can get a summary of skipped or running CI jobs for an OpenHarmony PR. The tool classifies per-job CI status including running, pending, and skipped states, alongside explicit failure reasons.

How do I retrieve all build artifacts instead of only failure logs in OpenHarmony CI?

To retrieve all build artifacts instead of only failure logs, adjust the log fetching mode. The tool supports fetching none, only failures, or every job with artifacts from the DCP event data.

Does the OpenHarmony CI status tool output JSON for automated debugging workflows?

Yes, the OpenHarmony CI status tool outputs JSON for automated debugging workflows. It provides controllable log modes and job-level results structured for programmatic consumption from GitCode PR context.

What is the best way to diagnose OpenHarmony CI failure causes from a PR URL?

The best way to diagnose OpenHarmony CI failure causes from a PR URL is using an automated script that resolves the DCP event, classifies job outcomes, and tails logs for failed jobs.