Makefile Validator

Makefile Validator

Validation Capabilities

• Syntax: GNU make -n --dry-run validation; catches errors with line numbers
• Formatting: mbake tab indentation, variable assignment consistency, trailing whitespace, line continuations
• Best practices: .DELETE_ON_ERROR, .PHONY declarations, $(MAKE) for recursive calls, .ONESHELL error handling
• Security: hardcoded credentials, unsafe variable expansion in rm/sudo/curl/wget, command injection, .EXPORT_ALL_VARIABLES leakage
• Optimization: .NOTPARALLEL, .INTERMEDIATE/.SECONDARY, VPATH usage, incremental build efficiency

See references/best-practices.md, references/common-mistakes.md, and references/bake-tool.md for detailed explanations.

Quick Start

Basic Validation

# Validate a Makefile
bash scripts/validate_makefile.sh Makefile

Example Output

========================================
MAKEFILE VALIDATOR
========================================
File: Makefile

[SYNTAX CHECK (GNU make)]
✓ No syntax errors found

[MBAKE VALIDATION]
✓ mbake validation passed

[MBAKE FORMAT CHECK]
⚠ Formatting issues found
Run 'mbake format Makefile' to fix formatting issues
Or run 'mbake format --diff Makefile' to preview changes

[CUSTOM CHECKS]
⚠ No .PHONY declarations found
✗ Potential spaces instead of tabs in recipes detected
ℹ No VPATH/vpath declarations found

========================================
VALIDATION SUMMARY
========================================
Errors:   1
Warnings: 2
Info:     1
⚠ Validation PASSED with warnings

Exit Codes

• 0: No issues found
• 1: Warnings found (passed with warnings)
• 2: Errors found (failed validation)

Common Validation Scenarios

Scenario 1: Pre-commit Validation

bash scripts/validate_makefile.sh Makefile

Scenario 2: Formatting Consistency

# Preview changes
mbake format --diff Makefile

# Apply formatting
mbake format Makefile

# Re-validate
bash scripts/validate_makefile.sh Makefile

Scenario 3: Converting Legacy Makefiles

# 1. Validate current state
bash scripts/validate_makefile.sh legacy.mk

# 2. Fix critical errors (tabs, syntax), then apply formatting
mbake format legacy.mk

# 3. Add .PHONY declarations
mbake format --auto-insert-phony-declarations legacy.mk

# 4. Re-validate
bash scripts/validate_makefile.sh legacy.mk

# 5. Reference best-practices.md for modernization guidance

Scenario 4: Security Audit

The validator automatically checks for hardcoded credentials, unsafe variable expansion in dangerous commands, and command injection vulnerabilities. Reference references/common-mistakes.md for detailed explanations and fixes.

Integration with Development Workflow

For pre-commit hooks, CI/CD pipelines (e.g. GitHub Actions), and self-validating Makefile targets, use the validation script at scripts/validate_makefile.sh and match on files named Makefile, makefile, or *.mk. The script's exit codes (0/1/2) map cleanly to pass/warn/fail states for any automation context. See references/bake-tool.md for CI/CD configuration details.

Installation Requirements

Required

• python3, pip3: For venv and mbake installation
• bash: For running validation script
• GNU make: For syntax validation (make -n)

Optional (Recommended)

• checkmake: Additional linting (minphony, phonydeclared rules)

  go install github.com/checkmake/checkmake/cmd/checkmake@latest
  

• unmake: POSIX portability checks — see github.com/mcandre/unmake

Automatic Installation

mbake is automatically installed in an isolated venv per invocation and cleaned up on exit — no manual installation required.

Directory Structure

makefile-validator/
├── skill.md                    # This file
├── scripts/
│   └── validate_makefile.sh    # Main validation script
├── references/
│   ├── best-practices.md       # Makefile best practices
│   ├── common-mistakes.md      # Common Makefile mistakes
│   └── bake-tool.md            # mbake tool reference (config, CI/CD, advanced features)
└── assets/
    ├── good-makefile.mk        # Well-written example
    └── bad-makefile.mk         # Anti-patterns example

Anti-Patterns

NEVER use spaces instead of tabs for recipe indentation

• WHY: GNU Make requires a hard tab character to start recipe lines. Spaces silently produce missing separator errors that are notoriously confusing.
• BAD: two spaces then echo "building" (spaces instead of tab)
• GOOD: \techo "building" (hard tab — \t)
• DETECTION: scripts/validate_makefile.sh catches this; run make -n to surface the error.

NEVER omit .PHONY for non-file targets

• WHY: Without .PHONY, if a file named clean or test exists, Make will silently skip the target because it considers it up-to-date.
• BAD: clean: with no .PHONY declaration
• GOOD: .PHONY: clean test build all declared at the top

NEVER use bare $(shell ...) calls in recipe variables without quoting

• WHY: Unquoted shell variable expansion in rm, sudo, or curl commands enables command injection when variable values contain spaces or special characters.
• BAD: rm -rf $(DIR) when DIR can be user-controlled
• GOOD: rm -rf "$(DIR)" or validate that DIR does not contain path separators

NEVER use recursive make with a bare make command

• WHY: Bare make in a recipe does not inherit the jobserver flags passed by the parent make, breaking parallel builds and potentially starting a separate build chain with different settings.
• BAD: make -C subdir
• GOOD: $(MAKE) -C subdir

NEVER export all variables globally with .EXPORT_ALL_VARIABLES

• WHY: Every variable in scope (including secrets loaded from .env files) gets exported to every sub-process, creating credential leakage risk.
• BAD: .EXPORT_ALL_VARIABLES: at top of Makefile
• GOOD: Use explicit export VAR only for variables that need sub-process visibility

Known Limitations

mbake doesn't recognize some valid GNU Make special targets (.DELETE_ON_ERROR, .SUFFIXES, .ONESHELL, .POSIX) — the validator filters these false positives and surfaces them as informational messages. The mbake format --check vs mbake format output may also differ; this is a known upstream issue. See references/bake-tool.md for full details including mbake configuration (~/.bake.toml) and format-disable comments.

References

Internal:

• Makefile Best Practices — idiomatic target patterns, variable scoping, and build organization guidelines
• Common Makefile Mistakes — detailed explanations of errors caught by the validator with fixes
• mbake Tool Reference — mbake configuration, CI/CD integration, and format-disable comments

External:

• GNU Make Manual — canonical reference for GNU make syntax, special targets, and built-in variables
• mbake GitHub — source and issue tracker for the mbake formatter
• checkmake GitHub — optional linter for .PHONY and rule declaration checks