makefile-linterLint Makefiles for common issues — tabs, .PHONY, unused vars, portability, and best practices.
Install via ClawdBot CLI:
clawdbot install charlie-morrison/makefile-linterGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Generated Jul 27, 2026
Integrate Makefile linting into continuous integration pipelines to catch errors early, enforce best practices, and ensure portability across environments. This prevents build failures due to misconfigured Makefiles.
Use makefile-linter to audit Makefiles in open source repositories before release, ensuring contributions follow community standards. This maintains project consistency and reduces maintenance overhead.
Lint Makefiles for embedded projects to detect hardcoded paths and shell portability issues, which are common in cross-compilation setups. This streamlines builds across different development environments.
Audit Makefiles used in infrastructure automation to enforce tab usage, complete .PHONY declarations, and avoid recursive make calls. This improves reliability of deployment pipelines.
Instruct students or new developers on proper Makefile creation by running lint and audit commands. The tool provides clear feedback on errors and warnings, accelerating the learning curve.
Offer the core linting tool for free, while charging for plugins that integrate with popular CI platforms (e.g., GitHub Actions, Jenkins) and provide advanced reporting dashboards.
Provide a cloud-based service where users upload Makefiles and receive detailed reports. Additional features like team collaboration and historical analysis are available via monthly subscription.
Offer professional consulting to companies needing to standardize Makefile practices, along with workshops on Makefile best practices. The tool is used as a training aid.
💬 Integration Tip
Integrate makefile-linter into your CI pipeline by running 'lint' with --format json and --strict to fail the build on any issue, then parse the JSON output for detailed reporting.
Scored Jun 20, 2026
Control desktop applications on Windows — launch, close, focus, resize, move windows, simulate keyboard/mouse input, manage processes, control VSCode, read clipboard, and capture screen info. Use when the user wants to interact with any running program, switch windows, type text, press shortcuts, open files in VSCode, manage running processes, or get system display information.
Conduct rigorous, adversarial code reviews with zero tolerance for mediocrity. Use when users ask to "critically review" my code or a PR, "critique my code", "find issues in my code", or "what's wrong with this code". Identifies security holes, lazy patterns, edge case failures, and bad practices across Python, R, JavaScript/TypeScript, SQL, and front-end code. Scrutinizes error handling, type safety, performance, accessibility, and code quality. Provides structured feedback with severity tiers (Blocking, Required, Suggestions) and specific, actionable recommendations.
Coding style memory that adapts to your preferences, conventions, and patterns for consistent coding.
Pragmatic coding standards for writing clean, maintainable code — naming, functions, structure, anti-patterns, and pre-edit safety checks. Use when writing new code, refactoring existing code, reviewing code quality, or establishing coding standards.
Claude Code integration for OpenClaw. This skill provides interfaces to: - Query Claude Code documentation from https://code.claude.com/docs - Manage subagents and coding tasks - Execute AI-assisted coding workflows - Access best practices and common workflows Use this skill when users want to: - Get help with coding tasks - Query Claude Code documentation - Manage AI-assisted development workflows - Execute complex programming tasks
Plan, draft, version, and refine written content with enforced versioning and quality audits.