菜单
Run HyperBEAM integration tests. Starts a local Erlang HyperBEAM node and tests AOS processes on the full production stack. Use when user says 'test on HyperBEAM', 'run integration tests', or 'test the full stack'. Not for in-memory tests — use /test.
用 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 | test-hb |
| description | Run HyperBEAM integration tests. Starts a local Erlang HyperBEAM node and tests AOS processes on the full production stack. Use when user says 'test on HyperBEAM', 'run integration tests', or 'test the full stack'. Not for in-memory tests — use /test. |
| argument-hint | [test-file] |
| disable-model-invocation | true |
| allowed-tools | Bash, Read, Grep |
Run HyperBEAM integration tests. These spawn a real Erlang node — different from in-memory AOS tests (/test).
lsof -ti :10000-10010 | xargs -r kill -9 2>/dev/null || true
pkill -f beam.smp 2>/dev/null || true
.env.hyperbeam:grep '^CWD=' .env.hyperbeam 2>/dev/null | cut -d= -f2-
If .env.hyperbeam doesn't exist or has no CWD, STOP and tell the user:
No HyperBEAM configured. Integration tests require a HyperBEAM installation.
During project creation (
npx wao create), choose option 1 (clone) or 2 (link). Or configure it now:echo "CWD=/path/to/your/HyperBEAM" >> .env.hyperbeam
Then verify the path exists:
HB_DIR=$(grep '^CWD=' .env.hyperbeam | cut -d= -f2-)
test -d "$HB_DIR/src" && echo "HyperBEAM: OK" || echo "HyperBEAM: MISSING"
If MISSING, stop and tell the user the CWD path in .env.hyperbeam is invalid.
# Specific file (if argument provided)
yarn test $ARGUMENTS
# Default HyperBEAM tests
yarn test test/hyperbeam.test.js
The HyperBEAM class reads .env.hyperbeam automatically via dotenv, so it picks up the correct CWD.
erl -eval 'halt().')/test-hb again (it cleans up first)erl -eval 'halt().'.env.hyperbeam CWD path is validps aux | grep beam