dockerignore-linterLint, validate, and audit .dockerignore files for syntax issues, security risks, missing patterns, and optimization opportunities. Use when asked to lint, va...
Install via ClawdBot CLI:
clawdbot install charlie-morrison/dockerignore-linterGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Generated May 8, 2026
A DevOps engineer profiles a monorepo's Docker build context, identifies large unnecessary files like node_modules and build artifacts, and adds precise .dockerignore patterns to reduce context size by 70%, speeding up CI/CD pipelines.
A security team scans .dockerignore files across multiple microservices to ensure sensitive files like .env, .git, and SSH keys are excluded, preventing accidental inclusion in Docker images that could lead to credential leaks.
A technical lead uses the suggest command to generate project-type specific .dockerignore patterns for a new Python/Node.js service, ensuring best practices are applied from the start and reducing future context bloat.
An SRE integrates the linter into a GitHub Actions workflow to automatically reject pull requests that introduce improper .dockerignore files, enforcing a baseline of security and optimization across the organization's container builds.
Offer a basic linter for free (local use) with premium features like advanced security patterns, CI integration templates, and multi-project audits via a subscription. Revenue from monthly or annual plans for teams.
Integrate the linter into a container registry or CI/CD platform as an add-on service. Charge per scan or per repository, providing ongoing security and optimization reports. Revenue from usage-based billing.
Provide manual or automated audits for organizations seeking to optimize Docker builds. Deliver a detailed report with actionable recommendations. Revenue from one-time consulting fees or annual audit contracts.
💬 Integration Tip
Add the linter to your CI pipeline by running `python3 scripts/dockerignore_linter.py lint .dockerignore --strict` to fail builds on issues, and use the context command to preview build sizes before pushing images.
Scored May 8, 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.