skills.rest
hpsgd
hpsgdOFFICIAL
Explore all skills by this author →
WebsiteGitHub

write-dockerfile

Generate multi-stage Dockerfiles with security hardening and .dockerignore rules.

Updated Apr 1, 2026
Search Tags:#automation#devops#security#docker#dockerfile#multistage-build
One-click install
npx skills add https://github.com/hpsgd/claude-marketplace --skill write-dockerfile
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: write-dockerfile
Source: https://github.com/hpsgd/claude-marketplace/tree/main/plugins/engineering/devops/skills/write-dockerfile
Command: npx skills add https://github.com/hpsgd/claude-marketplace --skill write-dockerfile

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Dockerfile creation for services is time-consuming and error-prone; this skill automates secure, multi-stage Dockerfile generation to ensure reproducible builds.

Core Features & Use Cases

  • Multi-stage builds that minimize runtime images and cache effectively.
  • Security hardening with non-root users, HEALTHCHECKs, and restricted permissions.
  • Easy integration with CI/CD via ready-to-use outputs and optional docker-compose adjustments.

Quick Start

Use the write-dockerfile skill to generate a secure multi-stage Dockerfile for your service.

Frequently Asked Questions about write-dockerfile

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

FAQPage Schema
How do I create a secure multi-stage Dockerfile for production?▼

A secure multi-stage Dockerfile for production is generated by automating multi-stage builds, non-root users, HEALTHCHECKs, and pinned base images to minimize runtime images and ensure reproducible builds across CI/CD pipelines.

What is the best way to automate Dockerfile creation for CI/CD pipelines?▼

Automating Dockerfile creation for CI/CD pipelines is best handled by generating ready-to-use outputs with security hardening, mandatory .dockerignore files, and optional docker-compose integration to ensure safe and maintainable containers.

Does Dockerfile security hardening require non-root users and HEALTHCHECKs?▼

Dockerfile security hardening requires specifying non-root users and HEALTHCHECKs to enforce restricted permissions and ensure safe, maintainable containers in production environments.

Why do I need a .dockerignore file for Dockerized stacks?▼

A .dockerignore file is mandatory for Dockerized stacks to prevent unnecessary files from entering the build context, ensuring reproducible images and effective caching during multi-stage builds.

Can I integrate docker-compose adjustments with generated Dockerfiles?▼

You can integrate docker-compose adjustments with generated Dockerfiles by utilizing the optional docker-compose integration feature to align your secure, multi-stage builds with existing orchestration configurations.

When should I use pinned base images in a multi-stage build?▼

Pinned base images should be used in a multi-stage build whenever reproducible images across CI/CD pipelines are required, preventing unexpected breaking changes from upstream tag updates.

Related Skills

Explore More Software Engineering Skills→
santosomarsantosomar
1

containerization-assistant

Generate hardened multi-stage Dockerfiles and .dockerignore files with stack detection.

Community
Advanced
ils15ils15
10

docker-deployment

Automate Docker deployments with multi-stage builds, health checks, and CI/CD pipelines.

Community
Advanced
jrollinjrollin
2

docker-expert

Optimize Dockerfiles with multi-stage builds and layer caching.

Community
Advanced
TKlerxTKlerx

multi-stage-dockerfile

Generate multi-stage Dockerfiles separating build-time from runtime dependencies.

Community
Intermediate