菜单
Classifies build, lint, and test failures into category (compile, lint, unit, ui, env-infra) and fixability tier only—no file edit instructions. Use after harmony-log-analyzer output or when routing HarmonyOS hvigor, codelinter, hdc, or on-device test failures in an autofix loop.
用 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 | test-failure-classifier |
| description | Classifies build, lint, and test failures into category (compile, lint, unit, ui, env-infra) and fixability tier only—no file edit instructions. Use after harmony-log-analyzer output or when routing HarmonyOS hvigor, codelinter, hdc, or on-device test failures in an autofix loop. |
Role: Type and tier only. It does not say which files to edit or how—harmony-fix-strategy handles that.
| Category | Typical signals |
|---|---|
| compile | ArkTS/ets errors, hvigor Error in compile/compileArk, missing symbol, type errors |
| lint | codelinter non-zero exit, rule violations in code-linter.json5 output, static analysis errors from CodeLinter (not hvigor compile) |
| unit | Failed assert in src/test / Local test output, JUnit/arkxtest local failure, exit non-zero in no-device test phase |
| ui | UiTest / ohosTest / on-device test failure, selector not found, UI timeout, test under ohosTest path |
| env-infra | codelinter not found or not on PATH, hdc no target, simulator not booting, signing errors, SDK path wrong, OOM, install failure clearly environmental |
| unknown | Unparseable, mixed errors, or insufficient log |
| Tier | Meaning | Typical next step |
|---|---|---|
| agent_safe | Likely fixable in app or test with minimal change | Allow harmony-fix-strategy to propose code edits |
| agent_risky | Flake, race, or ambiguous test/product boundary | harmony-fix-strategy may only propose test stabilization or ask user |
| human_required | signing, account, device farm, org policy, SDK install | Stop the loop; checklist for the user. No broad refactors |
.cursor/ohos-dev-commands.md failure order).category: ...tier: agent_safe | agent_risky | human_requiredone_line_summary: ...Do not add “edit Foo.ets line 12” here—that belongs in harmony-fix-strategy.