makefile-pro
/makefile-pro
Generate, scaffold, validate and lint Makefiles and .mk files: .PHONY targets, build automation, common mistakes. Use for any Makefile work.
- Author
- hybridlabor-api ↗
- Repository
- aos ↗
- Licence
- Apache-2.0
- Last repository change
- 14.10.2026
Assessment and security
- Files in this package
- 20
- Scripts
- 5
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 14.10.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
- 5 scripts in this package. Review them before installing, as Claude may execute them.
Scripts: generator/scripts/add_standard_targets.sh, generator/scripts/generate_makefile_template.sh, generator/test/test_helper_scripts.sh, validator/scripts/test_validate.sh, validator/scripts/validate_makefile.sh
What it does and when to use it
Generate, scaffold, validate and lint Makefiles and .mk files: .PHONY targets, build automation, common mistakes. Use for any Makefile work.
Original author description
Generate, scaffold, validate and lint Makefiles and .mk files: .PHONY targets, build automation, common mistakes. Use for any Makefile work.
How it works
- Generate
- Validate
SKILL.md preview
--- name: makefile-pro description: "Generate, scaffold, validate and lint Makefiles and .mk files: .PHONY targets, build automation, common mistakes. Use for any Makefile work." category: engineering-method --- # Makefile Pro One entry point for Makefile work, covering two phases: generating a new production-ready Makefile and validating or linting an existing one. Covers C/C++, Python, Go, Java and generic projects, GNU Coding Standards targets, security hardening and CI integration. Generation is requirements-first (language, structure, targets, install layout) with validation as a mandatory final step; validation is a local-first, deterministic pipeline whose exit codes decide whether fixes are optional, recommended, or required. Pick the section below by the request: "create/generate/write a Makefile" → Generate; "validate/lint/check/review a Makefile" → Validate. ## Generate - Use when a Makefile is created from scratch or manual build steps are converted to targets; do not use it for validating existing files or running builds. - Gather requirements first: language (C/C++, Python, Go, Java), project structure (single/multi-directory), build artifacts, install layout (default `PREFIX=/usr/local`), and which standard targets (all, install, clean, test, dist, help) are needed. - Ask the user only when information is missing or ambiguous (language, structure, registry, single vs. multiple binaries, cross-compilation); otherwise proceed with standard defaults. - Perform a documentation lookup for unfamiliar territory: Docker/container targets, CI platform integration (GitHub Actions, GitLab CI, Jenkins), cross-compilation, package managers (Conan, vcpkg, Homebrew), multi-binary projects, or version embedding via ldflags. - Built-in quality bar: GNU Coding Standards compliance, security hardening, dependency tracking, and automatic validation as the final step of every generation. - Always run validation on the generated file before handing it back (see Validate). - Full guide: generator/GUIDE.md - Helper scripts live in generator/scripts/. ## Validate - Use when checking an existing Makefile or `.mk` file: quality, linting, hardening, security or troubleshooting before CI. - Default entrypoint, run for every check: ```bash bash scripts/validate_makefile.sh <makefile-path> ``` - Layers run in order: dependency preflight (`python3`, `pip3`, `make`), GNU make syntax check (`make -n --dry-run`), `mbake validate`, `mbake format --check`, custom security/best-practice/optimization checks, plus optional `checkmake` and `unmake` when installed. - Exit codes: `0` = passed, `1` = passed with warnings (fix recommended, merge-policy dependent), `2` = failed — errors must be fixed and the run repeated. - Record the command, exit code, and error/warning/info counts from every run; open reference docs only for the finding types actually reported. - Fix, rerun, and stop when no new errors appear; document any warnings accepted intentionally and always report the latest exit code. - Full guide: validator/GUIDE.md
Files in this package (20)
- SKILL.md 3 KB
- generator/GUIDE.md 21 KB
- generator/assets/templates/.gitkeep 1 KB
- generator/docs/makefile-structure.md 11 KB
- generator/docs/optimization-guide.md 16 KB
- generator/docs/patterns-guide.md 12 KB
- generator/docs/security-guide.md 8 KB
- generator/docs/targets-guide.md 13 KB
- generator/docs/variables-guide.md 13 KB
- generator/scripts/add_standard_targets.sh 14 KB
- generator/scripts/generate_makefile_template.sh 15 KB
- generator/test/test_helper_scripts.sh 9 KB
- validator/GUIDE.md 7 KB
- validator/docs/bake-tool.md 21 KB
- validator/docs/best-practices.md 18 KB
- validator/docs/common-mistakes.md 19 KB
- validator/examples/bad-makefile.mk 2 KB
- validator/examples/good-makefile.mk 3 KB
- validator/scripts/test_validate.sh 16 KB
- validator/scripts/validate_makefile.sh 27 KB
Versions
The database has no other skills named makefile-pro.
Database snapshot: 13.11.2026 · package version 0254592f93e9 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 93makefile-generator
Generate GNU Make build systems that define build targets, configure dependencies, set up phony targets, and implement parallel builds. Use when creating make/Makefile/.mk files, implementing compile rules, or building production-ready build automation for C/C++, Go, Python, and Java projects. - 100makefile-authoring-and-validation
Authors Makefiles as a build/automation entry point for ops tasks — `.PHONY` target conventions, dependency graphs between targets, variable/default handling, and self-documenting `help` targets — and validates them with `make -n` (dry-run) and `checkmake`/shellcheck-style… - 90makefile-design
Write Makefiles with honest dependencies, phony discipline, and self-documenting help, and know when make is the wrong tool. Use when standardizing project task-running or fixing rebuild bugs. - 95makefile-validator
Comprehensive toolkit for validating, linting, and optimizing Makefiles. Use when working with Makefiles (Makefile, makefile, *.mk files), validating build configurations, checking for best practices, identifying security issues, or debugging Makefile problems. Concrete… - 100makefile
Best practices for authoring GNU Make Makefiles Triggers on: **/Makefile, **/makefile, **/*.mk, **/GNUmakefile - 100configure-makefile
Makefile with standard targets (help, test, build, clean, lint). Use when setting up a Makefile, auditing missing targets, or adding language-specific targets.