skills.rest
y1feng200156
y1feng200156COMMUNITY
Explore all skills by this author →
WebsiteGitHub

docker-lint

linting Dockerfiles for HELLO WORLD spam and unwanted content.

33|5|Updated Jan 2, 2026
Search Tags:#best practices#performance#security#dockerfile#linter#hadolint
One-click install
npx skills add https://github.com/y1feng200156/ham-study --skill docker-lint
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: docker-lint
Source: https://github.com/y1feng200156/ham-study/tree/main/.agent/skills/docker-lint
Command: npx skills add https://github.com/y1feng200156/ham-study --skill docker-lint

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of checking Dockerfiles against industry best practices, identifying potential security vulnerabilities, performance bottlenecks, and common errors before building container images.

Core Features & Use Cases

  • Security Auditing: Detects insecure configurations like running as root, unpinned package versions, and missing security headers.
  • Performance Optimization: Identifies opportunities to improve build times and image size through layer caching and efficient commands.
  • Compliance Checks: Enforces adherence to Docker's official best practices and standards.
  • Use Case: Before deploying a new microservice, use this Skill to scan its Dockerfile to ensure it meets security and performance benchmarks, preventing potential issues in production.

Quick Start

Use the docker-lint skill to check the Dockerfile in the current directory.

Frequently Asked Questions about docker-lint

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check my Dockerfile for security vulnerabilities and performance issues?▼

You can check your Dockerfile for security and performance issues by running it through a linter like hadolint, which scans for insecure configurations, unpinned package versions, and poor layer caching to ensure adherence to best practices.

What are common Dockerfile best practices I should enforce before building a container image?▼

Common Dockerfile best practices to enforce include executing as a non-root user, pinning package versions to specific releases, and optimizing layer caching to improve build times and reduce image size.

Can I scan multiple Dockerfiles recursively within a project directory?▼

Yes, you can scan multiple Dockerfiles recursively within a directory. The linter supports scanning single files as well as scanning recursively through a directory structure to validate all configurations.

Does the Dockerfile linter support custom configuration files for specific project rules?▼

Yes, the Dockerfile linter supports custom configuration files. This allows you to tailor the security, performance, and compliance checks to match your specific project requirements and enforce internal standards.

Why does my Docker build run as root and how do I identify this security risk?▼

Running as root is a security risk identified during Dockerfile security auditing. The linter detects insecure configurations like missing non-root user execution directives and flags them for remediation before deployment.

Related Skills

Explore More Software Engineering Skills→
AgentSecOpsAgentSecOps
183

container-hadolint

Lint Dockerfiles for security best practices and CIS Docker Benchmark compliance.

Official
Advanced
andrewwintandrewwint

dockerfile-builder

Generate optimized Dockerfiles with layer caching, security, and health checks.

Community
Intermediate
salmanabdurrahmansalmanabdurrahman

container-docker

Audit Docker daemons, images, and container runtimes for misconfigurations and vulnerabilities.

Community
Advanced
ToanPV90ToanPV90

container-scanning

Scan container images for vulnerabilities and misconfigurations using Trivy and Grype.

Community
Advanced