一键导入
build-and-test
Generic finalize prompt for discovering and running a repository's build and test checks when no repo-specific top-level skill has been written yet.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Generic finalize prompt for discovering and running a repository's build and test checks when no repo-specific top-level skill has been written yet.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Interactive setup for .harbor/runtime-target.json — chooses local/ssh mode and the game-RE target subobject (emulator, device, game window) plus a probe_command. Use when initializing a new repo, switching emulators, swapping target devices, or when target-runtime-exec reports a misconfiguration.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements, and design before implementation.
Use when project execution should follow the repo's selected runtime target instead of assuming the local machine. This covers build, test, run, deploy, migration, codegen, or environment-bootstrap commands that should route through `scripts/shared/target_runtime.py` when `.workflow/runtime-target.json` selects SSH.
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
Use when you have a spec or requirements for a multi-step task, before touching code. This is an executor skill - use only when a task has been picked up for implementation and you are in an executor session, NOT in a planner session.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
| name | build-and-test |
| description | Generic finalize prompt for discovering and running a repository's build and test checks when no repo-specific top-level skill has been written yet. |
Run the repository's normal build and test checks. This is a generic finalize default for newly bootstrapped downstream repos; replace it with repo-specific commands once the project workflow is known.
Read the local project files before running commands:
README.md or equivalent setup docspyproject.tomlpackage.jsonMakefilePrefer explicit project scripts over guessed commands. If more than one plausible stack exists, choose the smallest check set that validates the files changed in the current work and state the reason.
Files:
Verify:
git status --short and the changed paths.If the repository does not yet document a runnable build or test command, emit blocked classification=contract and explain what command or project metadata is missing. If a command exists but cannot run because of the local environment, emit blocked classification=env and include the failing command and error.