菜单
Post-build validation. Runs tests, checks Lua pitfalls, verifies AOS script coverage, and reports results. Use after building, before deploying, or when user says 'check everything', 'are tests passing', or 'validate'.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Full build workflow — plan, build, test, validate. Manages tasks.json throughout every step. Use when user says 'build this', 'start building', 'implement this feature', or 'make this'. Not for single-file fixes — use /build-aos, /build-device, or /build-module directly.
Run in-memory AOS tests (legacynet units). Fast unit testing — no server needed. Use when testing AOS scripts or after code changes. Not for HyperBEAM integration tests — use /test-hb instead.
Write AOS scripts and comprehensive in-memory tests. Iterates until all tests pass 100%. Use when user says 'build the AOS script', 'write the Lua code', or 'implement the handler'. Not for scaffolding — use /create-aos.
Write HyperBEAM Erlang device with eunit tests. Iterates until compilation and tests pass 100%. Use when user says 'build the device', 'write the Erlang code', or 'implement the device'. Not for scaffolding — use /create-device.
Write Vite + React frontend components with comprehensive vitest tests. 100% pass required. Use when user says 'build the frontend', 'write the UI', or 'implement the components'. Not for dev server — use /dev.
Build custom WASM64 (Rust) or standalone Lua modules with HyperBEAM integration tests. Iterates until all tests pass 100%. Use when user says 'build the module', 'write the WASM', 'custom Lua module', or 'implement the module'. Not for AOS scripts — use /build-aos.
| name | validate |
| description | Post-build validation. Runs tests, checks Lua pitfalls, verifies AOS script coverage, and reports results. Use after building, before deploying, or when user says 'check everything', 'are tests passing', or 'validate'. |
| argument-hint | [test-file] |
| disable-model-invocation | true |
| allowed-tools | Bash, Read, Grep, Glob |
Run post-build validation to verify code quality before declaring a task done.
Run in-memory AOS tests (mainnet WASM device):
yarn test $ARGUMENTS 2>&1
If $ARGUMENTS is empty, run the full suite: yarn test
If any tests fail, report the failures and stop. Do not proceed until all tests pass.
If HyperBEAM/ directory exists and Erlang is available:
yarn test test/hyperbeam.test.js 2>&1
Skip this gate if HyperBEAM is not set up. Report "skipped (no HyperBEAM)" in the summary.
If custom-lua/ or custom-wasm/ directory exists and has module files:
ls test/*-module.test.js 2>/dev/null && yarn test test/*-module.test.js 2>&1
Skip this gate if no custom modules. Report "skipped (no custom modules)" in the summary.
If frontend/ directory exists:
cd frontend && npm run test:unit 2>&1
Skip this gate if no frontend. Report "skipped (no frontend)" in the summary.
Run the validation script:
bash .claude/skills/validate/scripts/check-lua.sh
If the script reports issues, fix them before proceeding.
The script checks for:
Send().receive() — broken on genesis-wasmHandlers.addbint() without require('.bint')json.encode/json.decode without require('json')Verify AOS script coverage:
Handlers.add calls in src/*.luatest/*.test.jsCheck for uncaught error paths:
msg.Tags.* without nil checksbint() on potentially nil valuesReport a summary:
## Validation Results
Gate 1 — Unit tests: X passed, Y failed
Gate 2 — HyperBEAM: PASS / FAIL / skipped (no HyperBEAM)
Gate 3 — Custom modules: PASS / FAIL / skipped (no custom modules)
Gate 4 — Frontend tests: PASS / FAIL / skipped (no frontend)
Lua pitfalls: none found (or list issues)
AOS script coverage: X/Y AOS scripts have tests
Uncaught errors: none found (or list issues)
Overall: PASS / FAIL