docker-build

Build Docker images with Git SHA and timestamp tags for registries.

18|2|Updated Dec 12, 2025
One-click install
npx skills add https://github.com/markus41/claude --skill docker-build-markus41
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docker-build
Source: https://github.com/markus41/claude/tree/main/.claude/skills/docker-build
Command: npx skills add https://github.com/markus41/claude --skill docker-build-markus41

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures Docker images are built with proper, traceable tags and prevents issues caused by stale or improperly managed image versions.

Core Features & Use Cases

  • Automated Tagging: Generates unique tags using Git SHA and timestamps.
  • Cache Busting: Supports building with --no-cache for production.
  • Registry Verification: Includes steps to verify images in registries like ACR or Docker Hub.
  • Use Case: Automate the Docker image build process for a CI/CD pipeline, ensuring each build is uniquely identified and verifiable in the container registry.

Quick Start

Build the Docker image for the current project using the docker-build skill.

Frequently Asked Questions about docker-build

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

FAQPage Schema
How do I tag Docker images with Git SHA and timestamps for CI/CD pipelines?

Tag Docker images with Git SHA and timestamps by automating the build process to generate unique, traceable tags for each specific branch, ensuring every build is properly identified and verifiable in the container registry.

What is cache busting in Docker builds and when do I need it for production?

Cache busting in Docker builds uses the `--no-cache` flag to force a fresh build without stale layers. You need it for production builds to prevent issues caused by improperly managed or outdated image versions.

Can I verify Docker images in a container registry like ACR or Docker Hub after building?

Yes, you can verify Docker images in registries like ACR or Docker Hub. The build process includes automated verification steps to confirm that the uniquely tagged images are successfully pushed and available.

Why does my CI/CD pipeline deploy stale Docker image versions?

Your pipeline deploys stale Docker image versions due to improper tag management. Solve this by generating unique tags using Git SHA and timestamps, incorporating cache busting with `--no-cache` for production builds.

What's the best way to automate Docker image tagging for specific branches?

The best way to automate Docker image tagging for specific branches is using an automated build process that generates unique tags based on Git SHA and timestamps, then pushes them directly to your container registry with verification.