hammer-build-validate

Build validation automates compilation checks, crash detection, and test execution to verify your changes don't break the codebase. This Skill runs a debug build, smoke tests for crashes, core tests, and generates a summary report at /tmp/hammer_build_validation_report.md, catching issues before PR submission.

Yes, smoke testing runs the application briefly to catch immediate crashes, segmentation faults, assertion failures, and critical SDL errors that occur on startup, ensuring the build is crash-free before proceeding to full testing.

Build validation requires cmake for compilation, ninja for parallel builds, and timeout to manage process execution. These tools orchestrate the complete validation pipeline from clean build through test execution.

The validation pipeline detects and categorizes compilation warnings and errors during the debug build phase, providing a clean codebase assessment. Warnings are counted and included in the summary report so you can address them before integration.

Yes, build validation applies to daily validation workflows and pre-PR checks. The complete pipeline—clean build, crash-free smoke testing, core test suite, and structured reporting—fits into automated CI/CD pipelines for continuous codebase health monitoring.