makefile-validator

To validate a Makefile, run the validator script with your file path to perform GNU Make dry-run checks and mbake-based rules. This catches syntax errors, anti-patterns, and unsafe practices to prevent broken builds in local development and CI workflows.

Linting Makefiles in a CI pipeline is best handled by running deterministic validation checks against your build scripts. This validator applies layered preflight checks, including syntax, best practices, and optional portability checks, to enforce consistent Makefile quality.

Yes, you need Python 3.9 or higher and GNU Make installed to check Makefile syntax. Python is required for the mbake dependency, while GNU Make handles the dry-run syntax checks, and optional tools like checkmake and unmake offer extended portability validation.

Yes, you can use checkmake and unmake for extended Makefile portability checks. These optional tools integrate with the validator's layered checking approach to apply deeper preflight analysis beyond the standard GNU Make syntax and mbake best practice rules.

Makefile validation fails during local preflight checks when the validator detects syntax errors, anti-patterns, or unsafe practices using GNU Make and mbake. Running the validation script directly against your Makefile path identifies the specific build issues causing the failure.