메뉴
Runs HarmonyOS CodeLinter (codelinter) on the project after a successful HAP build, using code-linter.json5, and fixes reported issues. Use in autofix loops immediately after harmony-build, or when addressing static analysis / code style findings.
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-codelinter |
| description | Runs HarmonyOS CodeLinter (codelinter) on the project after a successful HAP build, using code-linter.json5, and fixes reported issues. Use in autofix loops immediately after harmony-build, or when addressing static analysis / code style findings. |
Role: Static analysis gate after compile. It does not replace hvigorw; it runs only after a successful assembleHap (or the manifest’s equivalent), unless the user explicitly runs lint-only.
.cursor/ohos-dev-commands.md section 1) Build — subsection CodeLinter (after successful build) — for the exact command and working directory.safe-command-policy: use the manifest line; do not invent new codelinter flags without updating the manifest.--fix, --exit-on).codelinter is not on PATHcodelinter is installed) is required, and point to the reference above.codelinter configured, re-run the manifest command after the environment is fixed.Proceed to harmony-unit-test in a full loop (see harmony-autofix-orchestrator), or continue the pipeline as orchestrated.
harmony-log-analyzer (console output of codelinter / report file if -o was used).test-failure-classifier: expect lint-style or compile-adjacent static issues; tier usually agent_safe for code fixes, env-infra if the tool is missing.harmony-fix-strategy allows edits: fix the listed files (prefer codelinter -c ./code-linter.json5 . --fix when safe, then hand-fix remaining issues).codelinter (or from harmony-build if a change may affect compile).Do not start the emulator solely because codelinter failed.
For deeper context on Hvigor, CodeLinter, state management, and UI patterns, use the copies under docs/arkts-references/ (see harmony-build and this skill for entry points).