skills/ohos-app-build-debug/SKILL.md
Build, install, launch, and debug HarmonyOS/OpenHarmony applications using DevEco Studio toolchain. Use when Claude needs to: (1) Build OHOS apps with hvigorw, (2) Install HAP files to devices via hdc, (3) Launch or debug OHOS applications, (4) Parse crash stacks with hstack, (5) Take device screenshots, or (6) Detect DevEco Studio environment and SDK tools. Automatically detects DevEco Studio installation and configures JAVA_HOME, PATH, and toolchain.
npx skillsauth add openharmonyinsight/openharmony-skills ohos-app-build-debugInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Use this skill when the user needs to work with HarmonyOS/OpenHarmony applications:
Build, install, and launch an OHOS application:
# Run scripts from skill directory
python3 $SKILL_DIR/scripts/build.py
python3 $SKILL_DIR/scripts/install.py -f entry/build/default/outputs/default/entry-default-signed.hap
python3 $SKILL_DIR/scripts/launch.py
This skill includes executable scripts in scripts/ that automatically detect DevEco Studio environment:
| Script | Purpose |
|--------|---------|
| build.py | Build OHOS application using hvigorw |
| install.py | Install HAP file to connected device |
| launch.py | Launch installed application |
| screenshot.py | Capture device screenshot |
| parse_crash.py | Parse crash stack using hstack |
| env_detector.py | Detect DevEco Studio and tools |
| ohos_utils.py | Shared utility functions |
For detailed command reference, see references/command-reference.md.
# 1. Check environment
python3 $SKILL_DIR/scripts/env_detector.py
# 2. Build the application
python3 $SKILL_DIR/scripts/build.py
# 3. Install to device (output from build.py shows HAP path)
python3 $SKILL_DIR/scripts/install.py -f entry/build/default/outputs/default/entry-default-signed.hap
# 4. Launch the app
python3 $SKILL_DIR/scripts/launch.py
python3 $SKILL_DIR/scripts/build.py && \
python3 $SKILL_DIR/scripts/install.py -f $(find entry/build -name "*.hap" | head -1) && \
python3 $SKILL_DIR/scripts/launch.py
# Launch app
python3 $SKILL_DIR/scripts/launch.py
# Take screenshot to verify
python3 $SKILL_DIR/scripts/screenshot.py -o ./screenshots
# Parse crash stack from file
python3 $SKILL_DIR/scripts/parse_crash.py -f crash.txt
# Parse from string
python3 $SKILL_DIR/scripts/parse_crash.py -c "stack trace here"
All scripts automatically detect DevEco Studio installation and configure the environment:
DevEco Studio Detection
C:\Program Files\Huawei\DevEco Studio\/Applications/DevEco-Studio.app/~/DevEco-Studio/ or /opt/DevEco-Studio/Toolchain Configuration
JAVA_HOME to DevEco's bundled JBRPATHHDC_SERVER_PORT=7035Auto-Detected Tools
When helping users with OHOS development:
Locate Skill Directory
$SKILL_DIR with the actual skill installation path~/.claude/skills/ohos-app-build-debug or project-specific pathsExecute Scripts
scripts/ directory using absolute or relative pathsShow Environment First
env_detector.py when first building to show tool availabilityProvide One-liners
Show Actual Commands
Handle Errors Gracefully
Use Project Context
If DevEco Studio is not detected:
DEVECO_STUDIO_PATH environment variableIf device is not connected:
For detailed troubleshooting, see references/troubleshooting.md.
Download DevEco Studio: https://developer.huawei.com/consumer/cn/doc/harmonyos-guides/ide-download
development
Run local code quality checks covering a subset of OpenHarmony gate CI (copyright, CodeArts C/C++) plus additional local checks (pylint/flake8, shellcheck/bashate, gn format). Use before committing to reduce gate failures. Triggers on: /oh-precommit-codecheck, "门禁检查", "门禁预检", "检查代码", "run codecheck", "check code quality", "lint my code", "代码检查", or after completing code implementation. WHEN to use: before git commit, before creating PR, after modifying C/C++/Python/Shell/GN files, when gate CI fails with codecheck defects, or when you want to preview what gate will flag.
development
OpenHarmony PR full lifecycle workflow. Five modes: - Commit: standardized commit with DCO sign-off and Issue linking - Create PR: commit + push to fork + create Issue + create PR on upstream - Fix Codecheck: fetch gate CI codecheck defects from a PR and auto-fix them - Review PR: fetch a PR's changes to local for code review - Fix Review: fetch unresolved review comments from a PR and auto-fix them Triggers on: /oh-pr-workflow, "提交代码", "创建PR", "提个PR", "commit", "修复告警", "修复门禁", "修复codecheck", "fix codecheck", "review pr", "review这个pr", "看下这个pr", "检视pr", "修复review", "修复检视意见", "fix review", or a GitCode PR URL with fix/review intent.
testing
分析 HM Desktop PRD 文档,提取需求信息、验证完整性、检查章节顺序(需求来源→需求背景→需求价值分析→竞品分析→需求描述)、检查 KEP 定义、检测需求冲突并生成结构化分析报告。适用于用户请求:(1) 分析或审查 PRD 文档, (2) 从需求中提取 KEP 列表, (3) 检查 PRD 完整性或一致性, (4) 将需求映射到模块架构, (5) 验证 PRD 格式合规性, (6) 验证竞品分析章节完整性。关键词:PRD分析, requirement extraction, KEP验证, completeness check, chapter order validation, 竞品分析检查, analyze PRD, 需求提取, 完整性检查, 章节顺序验证
development
基于 PRD 文档自动生成鸿蒙系统设计文档,包括架构设计文档和功能设计文档。生成前会分析 OpenHarmony 存量代码结构,确保与现有架构兼容。架构设计文档第2章必须为竞品方案分析,位于需求背景之后。适用于用户请求:(1) 生成架构设计文档, (2) 生成功能设计文档, (3) 从 PRD 生成设计文档, (4) 创建系统架构设计, (5) 编写功能规格说明, (6) 分析 OH 代码结构。关键词:architecture design, functional design, design doc, 竞品方案分析, OpenHarmony code analysis, 架构设计, 功能设计, 设计文档生成, OH代码分析, analyze codebase, competitor analysis