SkillsAdd

github/awesome-copilot · Official

multi-stage-dockerfile

Create optimized multi-stage Dockerfiles for any language or framework

All-time #1011 Trending #2030 First seen Feb 25, 2026
8-week activity · all time api

Installation

$ npx skills add github/awesome-copilot --skill multi-stage-dockerfile
View on skills.sh ↗ GitHub repository ↗
Feature your product here Skill page unit · reach builders installing agent skills View pricing →

Summary

  • Build optimized, secure multi-stage Dockerfiles for any language or framework.
  • Structures builds with separate builder and runtime stages, copying only necessary artifacts to minimize final image size and attack surface Emphasizes layer caching optimization by ordering commands from least to most frequently changing, combined with .dockerignore and command consolidation Recommends minimal base images (Alpine, distroless, or official slim variants) with exact version pinning for reproducibility Covers security hardening: non-root users, build tool removal, vulnerability scanning, and secrets isolation through multi-stage separation Includes performance patterns like build arguments, environment variable optimization, and healthcheck configuration for production readiness

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

dockerfile-validator Similar name
akin-ozer/cc-devops-skills

Validate, lint, audit, or scan a Dockerfile for security and best practices.

592 installs
dockerfile-generator Similar name
akin-ozer/cc-devops-skills

Create, generate, or write Dockerfiles and multi-stage Docker images. Containerize apps.

554 installs

Also in this package

Other skills from github/awesome-copilot · top by installs.

npx skills add github/awesome-copilot
git-commit 79 excalidraw-diagram-generator 53 documentation-writer 52 prd 34 refactor 17 gh-cli 21.2K java-springboot 36 create-readme 40 playwright-generate-test 8 github-issues 31

Browse all from github/awesome-copilot

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 38.8K
License LICENSE
Default branch main
Open issues 21
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents github-copilot

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,314 B
  • docs SUMMARY.md 100 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 23,501 installs

SKILL.md

Your goal is to help me create efficient multi-stage Dockerfiles that follow best practices, resulting in smaller, more secure container images.

Multi-Stage Structure

  • Use a builder stage for compilation, dependency installation, and other build-time operations
  • Use a separate runtime stage that only includes what's needed to run the application
  • Copy only the necessary artifacts from the builder stage to the runtime stage
  • Use meaningful stage names with the AS keyword (e.g., FROM node:18 AS builder)
  • Place stages in logical order: dependencies → build → test → runtime

Base Images

  • Start with official, minimal base images when possible
  • Specify exact version tags to ensure reproducible builds (e.g., python:3.11-slim not just python)
  • Consider distroless images for runtime stages where appropriate
  • Use Alpine-based images for smaller footprints when compatible with your application
  • Ensure the runtime image has the minimal necessary dependencies

Layer Optimization

  • Organize commands to maximize layer caching
  • Place commands that change frequently (like code changes) after commands that change less frequently (like dependency installation)
  • Use .dockerignore to prevent unnecessary files from being included in the build context
  • Combine related RUN commands with && to reduce layer count
  • Consider using COPY --chown to set permissions in one step

Security Practices

  • Avoid running containers as root - use USER instruction to specify a non-root user
  • Remove build tools and unnecessary packages from the final image
  • Scan the final image for vulnerabilities
  • Set restrictive file permissions
  • Use multi-stage builds to avoid including build secrets in the final image

Performance Considerations

  • Use build arguments for configuration that might change between environments
  • Leverage build cache efficiently by ordering layers from least to most frequently changing
  • Consider parallelization in build steps when possible
  • Set appropriate environment variables like NODE_ENV=production to optimize runtime behavior
  • Use appropriate healthchecks for the application type with the HEALTHCHECK instruction