القائمة
Validate voxtype binaries for CPU instruction contamination. Use when checking release binaries for AVX-512 or GFNI instruction leaks that would crash on older CPUs.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Build all voxtype binaries for release. Builds Whisper (AVX2, AVX-512, Vulkan) and ONNX (AVX2, AVX-512, CUDA) binaries using Docker. Use when preparing a new release.
Run regression tests for voxtype releases. Use before major releases to verify core functionality, CLI commands, and configuration handling.
Run interactive smoke tests for voxtype. Tests recording cycles, CLI overrides, signal handling, and service management. Use after installing a new build.
Triage a GitHub issue or PR by checking for duplicates, documentation alignment, project fit, and recommending labels.
Publish voxtype to AUR. Updates PKGBUILD, generates checksums, and pushes to AUR. Use after a GitHub release is published.
Test voxtype in Docker containers. Use for testing builds, verifying packages work on different distros, or isolating test environments.
| name | validate-binaries |
| description | Validate voxtype binaries for CPU instruction contamination. Use when checking release binaries for AVX-512 or GFNI instruction leaks that would crash on older CPUs. |
| user-invocable | true |
| allowed-tools | ["Bash","Read","Glob"] |
Verify that voxtype binaries don't contain forbidden CPU instructions that would cause crashes on older CPUs.
| Binary | Must NOT have | Must have |
|---|---|---|
| AVX2 | zmm registers, AVX-512 EVEX, GFNI | - |
| Vulkan | zmm registers, AVX-512 EVEX, GFNI | - |
| AVX-512 | - | zmm registers (confirms optimization) |
zmm registers - 512-bit AVX-512 registersvpternlog, vpermt2, vpblendm - AVX-512 specific{1to4}, {1to8}, {1to16} - AVX-512 broadcast syntaxvgf2p8, gf2p8 - GFNI instructions (not on Zen 3)When asked to validate binaries:
releases/${VERSION}/# Set version
VERSION=0.4.14
# Check AVX2 binary (should be 0 for all)
echo "=== AVX2 Binary ==="
objdump -d releases/${VERSION}/voxtype-${VERSION}-linux-x86_64-avx2 | grep -c zmm || echo "zmm: 0"
objdump -d releases/${VERSION}/voxtype-${VERSION}-linux-x86_64-avx2 | grep -cE 'vpternlog|vpermt2|vpblendm' || echo "AVX-512 ops: 0"
objdump -d releases/${VERSION}/voxtype-${VERSION}-linux-x86_64-avx2 | grep -cE 'vgf2p8|gf2p8' || echo "GFNI: 0"
# Check Vulkan binary (should be 0 for all)
echo "=== Vulkan Binary ==="
objdump -d releases/${VERSION}/voxtype-${VERSION}-linux-x86_64-vulkan | grep -c zmm || echo "zmm: 0"
objdump -d releases/${VERSION}/voxtype-${VERSION}-linux-x86_64-vulkan | grep -cE 'vgf2p8|gf2p8' || echo "GFNI: 0"
# Check AVX-512 binary (should be > 0)
echo "=== AVX-512 Binary ==="
objdump -d releases/${VERSION}/voxtype-${VERSION}-linux-x86_64-avx512 | grep -c zmm
PASS conditions:
FAIL conditions:
If validation fails, the Docker build cache is likely stale. Recommend:
docker compose -f docker-compose.build.yml build --no-cache avx2 vulkan