oh-pr-workflow
oh-pr-workflow: OpenHarmony PR Lifecycle Workflow
Unified workflow for OpenHarmony GitCode repositories. Five modes:
- Commit only: user says "提交", "commit" → commit with standardized message, stop
- Full PR: user says "创建PR", "提个PR" → commit (if needed) + push + Issue + PR
- Fix Codecheck: user says "修复告警", "修复门禁", "修复codecheck" or provides a PR URL → fetch gate codecheck defects and auto-fix
- Review PR: user says "review pr", "检视pr", "看下这个pr" + PR URL → fetch PR changes to local for review
- Fix Review: user says "修复review", "修复检视意见", "fix review" + PR URL → fetch unresolved review comments and auto-fix
Mode Selection (Quick Reference)
| User Intent | Mode | Skip to |
|---|---|---|
| "提交", "commit" | Mode 1: Commit Only | Mode 1 |
| "创建PR", "提个PR" | Mode 2: Full PR | Mode 2 |
| "修复告警", "修复门禁", "fix codecheck" + PR URL | Mode 3: Fix Codecheck | Mode 3 |
| "review pr", "检视pr" + PR URL | Mode 4: Review PR | Mode 4 |
| "修复review", "fix review" + PR URL | Mode 5: Fix Review | Mode 5 |
More from openharmonyinsight/openharmony-skills
openharmony-cpp
Expert coding guide for OpenHarmony C++ development. Use this skill when writing, refactoring, or reviewing C++ code for OpenHarmony projects. It enforces strict project-specific conventions (naming, formatting, headers) and critical security requirements (input validation, memory safety).
81openharmony-security-review
Use when reviewing OpenHarmony C++ system service code for security vulnerabilities, particularly IPC handlers, multithreaded components, or code handling sensitive user data
80oh-ut-generator
|
67cpp-core-guidelines-review
Parallel C++ Core Guidelines code review using multiple specialized sub-agents. Use when reviewing C++ code, modules, or files against C++ Core Guidelines to identify violations. Each sub-agent reviews against a specific guideline section (Functions, Classes, Resource Management, etc.) and outputs findings to separate markdown files in the review/ directory, followed by a consolidated summary.
60openharmony-build
This skill should be used when the user asks to "编译 OpenHarmony", "build OpenHarmony", "编译完整代码", "执行编译", "编译 OpenHarmony 代码", "快速编译", "跳过gn编译", "fast-build", "编译测试", "编译测试用例", "build ace_engine_test", "编译 sdk", "编译 SDK", "build sdk", "build SDK", "编译 ohos-sdk", "编译测试列表", "build test list", "按列表编译测试", "编译指定测试", or mentions building the full OpenHarmony system, fast rebuild, test compilation, SDK compilation, or building tests from a target list. Handles complete build process including build execution, success verification, and failure log analysis with primary focus on out/{product}/build.log.
58ohos-chromium-security-review
|
57