菜单
Gathers and summarizes failure evidence from Hvigor output, test reports, and hdc hilog in the order defined by the project manifest. Use after any failed build, unit, or UI test step in a HarmonyOS autofix flow.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use this skill when the user asks to release the iOS app, upload a build, submit to App Store Connect review, or "在 App Store 上架/提交审核" for WordMagicGame.
Seed a lesson-import draft on a deployed Happyword API (Preview or prod) and optionally run the extract-pending cron so it reaches `pending` (待复核). Uses tools starting with `hw_`. Invoke when the user wants to upload a textbook photo for review against a specific Vercel URL, mirror E2E `test_lesson_import_cron_e2e`, or smoke-test lesson import + cron on a branch deployment.
Investigate why a Vercel preview / production deployment of the FastAPI server is broken (404 on every path, 500 on every path, e2e CI red, etc.). Pulls the right log surface for the symptom and maps HTTP error headers to root causes. Use whenever the deployed server returns wrong responses, the server-ci e2e job fails, or autofix loops keep retrying without converging.
Health-check every active Vercel Preview deployment listed in the live manifest at `https://happyword.cool/api/v1/public/preview-urls.json`. Probes `GET /api/v1/public/health` through Vercel Deployment Protection (`x-vercel-protection-bypass` header), prints a one-line status per preview, and exits non-zero if any are sick. Use when the user asks to "test preview health", "check previews", "are PR previews alive?", before merging anything that touches `server/`, after a fleet-wide redeploy or env-var rotation, or after rotating `VERCEL_AUTOMATION_BYPASS_SECRET` — do NOT loop ad-hoc `curl` calls or use `tools/vercel/smoke-prod.sh` (production-only) for this.
Drives a per-feature visual + spec-anchored gap scout across HarmonyOS / iOS / Android using tools/parity_scout/. Use when asked to "find iOS / Android gaps vs HarmonyOS main", "check parity for <feature>", or "screenshot the three platforms and tell me what's different".
Drives a per-feature visual + spec-anchored gap scout across HarmonyOS / iOS / Android using tools/parity_scout/. Use when asked to "find iOS / Android gaps vs HarmonyOS main", "check parity for <feature>", or "screenshot the three platforms and tell me what's different".
| name | harmony-log-analyzer |
| description | Gathers and summarizes failure evidence from Hvigor output, test reports, and hdc hilog in the order defined by the project manifest. Use after any failed build, unit, or UI test step in a HarmonyOS autofix flow. |
Read section 5 (Failure artifacts) in .cursor/ohos-dev-commands.md. Follow that read order literally.
entry/build/** for *report*, *test*, or test-results style outputs (paths vary; note what you find for this run).hdc hilog (or team-standard filter) after reproducing, if the failure is on-device.test-failure-classifier only)excerpt (key errors, a few short blocks, not the whole build).paths_found: list of report or log file paths you actually read.failed_phase: build | codelinter | unit | emulator | ui (which step produced the primary error).Do not assign edit instructions; test-failure-classifier and harmony-fix-strategy do that.