菜单
Runs complete build validation pipeline for SDL3 VoidLight-Framework including Debug build, smoke test execution, core test suite, and summary report generation. Use when the user wants to quickly validate their changes, check if the codebase is in a good state, or run the standard daily validation workflow.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Runs performance benchmarks for SDL3 VoidLight-Framework and detects regressions by comparing metrics against baseline. Use when testing performance-sensitive changes to AI, collision, pathfinding, particle systems, or before merging features to ensure no performance degradation.
Generates professional performance analysis reports from SDL3 VoidLight-Framework benchmark results including statistical analysis, comparison tables, visualizations, and recommendations. Use when preparing performance documentation, analyzing optimization efforts, or generating milestone/release reports.
Generates comprehensive, professionally-formatted changelogs for SDL3 VoidLight-Framework from git history. Analyzes code changes, runs tests, includes architect review, and produces detailed documentation as an ongoing engineering log. Use when documenting updates, preparing releases, or creating detailed change reports.
Verify dependency structure and architecture health for SDL3 VoidLight-Framework. Detects circular dependencies, excessive coupling, layer violations, header bloat, and provides dependency graph visualization. Ensures adherence to layered architecture (Core→Managers→States→Entities). Use monthly, after major refactors, or when investigating compile time issues.
Simplified memory profiling and leak detection for SDL3 VoidLight-Framework using valgrind memcheck, AddressSanitizer, and massif. Identifies memory leaks, allocation hotspots, buffer reuse violations, and provides system-by-system memory breakdown with optimization suggestions. Use after performance-critical changes or when investigating memory issues.
Runs comprehensive code quality checks for SDL3 VoidLight-Framework including compilation warnings, static analysis (cppcheck, clang-tidy), coding standards validation, threading safety verification, and architecture compliance. Use before commits, pull requests, or when the user wants to verify code meets project quality standards.
| name | voidlight-build-validate |
| description | Runs complete build validation pipeline for SDL3 VoidLight-Framework including Debug build, smoke test execution, core test suite, and summary report generation. Use when the user wants to quickly validate their changes, check if the codebase is in a good state, or run the standard daily validation workflow. |
| allowed-tools | ["Bash","Read","Write"] |
This Skill automates the standard build validation workflow for SDL3 VoidLight-Framework. It performs a complete validation cycle that developers typically run 5-10 times daily.
The Skill executes these steps in sequence:
Command:
cmake -B build/ -G Ninja -DCMAKE_BUILD_TYPE=Debug && ninja -C build
Validation:
ninja -C build -v 2>&1 | grep -E "(warning|unused|error)" | head -n 100
Error Handling:
Command:
timeout 60s ./bin/debug/VoidLight_Template > /tmp/app_log.txt 2>&1
Working Directory: $PROJECT_ROOT/
Validation:
/tmp/app_log.txt for:
Success Criteria:
Error Handling:
Command:
./tests/test_scripts/run_all_tests.sh --core-only --errors-only
Working Directory: $PROJECT_ROOT/
What This Runs:
The exact core suite is defined by the TEST_SCRIPTS array inside tests/test_scripts/run_all_tests.sh — do not assume a frozen list. Discover the current set at runtime instead of relying on a hardcoded snapshot:
# List the runner scripts that make up the suite
ls tests/test_scripts/run_*tests*.sh
# Or read the authoritative array the master runner executes
grep '\$SCRIPT_DIR/run_' tests/test_scripts/run_all_tests.sh
This covers the Core/Manager/Controller/Integration test runners (thread system, AI, behavior, event, collision, pathfinding, resource, world, particle, EDM, controllers, GPU, etc.). The count grows as systems are added, so derive it from the output above rather than embedding a number.
Validation:
Success Criteria:
Error Handling:
./tests/test_scripts/run_<system>_tests.sh --verbose
Report Format:
# Build Validation Report
**Date:** YYYY-MM-DD HH:MM:SS
**Branch:** <current-branch>
**Project:** SDL3 VoidLight-Framework
## Results Summary
✓/✗ **Build:** <Status> (<warning-count> warnings)
✓/✗ **Smoke Test:** <Status> (<exit-reason>)
✓/✗ **Core Tests:** <passed>/<total> passed
**Total Execution Time:** <time>
## Details
### Build Warnings (<count>)
<list of warnings if any, max 10>
### Test Failures (<count>)
<list of failed tests with brief errors>
### Recommendations
<specific actions based on failures>
---
**Status:** ✓ PASSED / ✗ FAILED
Save Location: /tmp/voidlight_build_validation_report.md
Console Output:
=== VoidLight-Framework Build Validation ===
✓ Build: Success (3 warnings)
✓ Smoke Test: Clean (60s timeout)
✓ Core Tests: <passed>/<total> passed # totals discovered from the runner, not fixed
Total Time: 3m 42s
Status: ✓ PASSED
Report: /tmp/voidlight_build_validation_report.md
When the user says:
Activate this Skill automatically.
$PROJECT_ROOT//tmp/ for user reviewThis Skill is designed to be run:
Build fails with linker errors:
rm -rf build/ && cmake -B build/ -G Ninja -DCMAKE_BUILD_TYPE=Debug && ninja -C buildSmoke test always crashes:
cmake -B build/ -G Ninja -DCMAKE_BUILD_TYPE=Debug \
-DCMAKE_CXX_FLAGS="-D_GLIBCXX_DEBUG -fsanitize=address -fno-omit-frame-pointer -g" \
-DCMAKE_EXE_LINKER_FLAGS="-fsanitize=address" \
-DUSE_MOLD_LINKER=OFF && ninja -C build
Tests hang indefinitely:
timeout 120s ./bin/debug/<test_name>High warning count:
ninja -C build -v 2>&1 | grep -E "warning" | sort | uniq