docker-build

Build Docker images with deterministic git SHA and timestamp tags.

8|Updated Mar 8, 2026

Search Tags:#devops #docker #registry #ci-cd #tagging #cache-busting #docker-build

Ready to run

npx skills add https://github.com/SufficientDaikon/archon --skill docker-build-sufficientdaikon

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: docker-build
Source: https://github.com/SufficientDaikon/archon/tree/main/skills/docker-build
Command: npx skills add https://github.com/SufficientDaikon/archon --skill docker-build-sufficientdaikon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Build Docker images with proper tagging, cache busting, and build tracking to prevent stale deployments.

Core Features & Use Cases

Generate deterministic image tags using git SHA and timestamps for traceability.
Implement cache-busting options for production builds and convenient tags for development.
Verify and push images to registries with dual-tag strategy (<branch>-latest) to simplify rollbacks.

Quick Start

Trigger a production build that tags the image with git SHA and timestamp, then push to the registry.

Frequently Asked Questions about docker-build

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

FAQPage Schema

How do I automate Docker image tagging with git SHA and timestamps for CI/CD pipelines?▼

Automate Docker image tagging by generating deterministic tags from a git SHA and timestamp. This ensures unique traceability for each build and reliable deployment provenance across your CI/CD pipelines.

Why do I need deterministic Docker tags and cache busting for production deployments?▼

Deterministic Docker tags and cache busting prevent stale deployments by ensuring each production build pulls fresh layers. This strategy guarantees that your deployments use the exact intended image version rather than cached, outdated artifacts.

What is the best way to tag Docker images for reliable rollbacks in a registry?▼

The best way to tag Docker images for rollbacks is a dual-tag strategy. Pushing both a specific git SHA tag and a branch-latest alias to your registry simplifies identifying stable versions and rolling back quickly.

Can I use dual-tagging for both development and production Docker builds?▼

Yes, you can use dual-tagging for both environments. Production builds utilize cache-busting and deterministic timestamps, while development builds receive convenient tags to streamline local workflows and testing.

How do I verify and push Docker images to a registry after building?▼

Verify and push Docker images by generating unique tags from a git SHA and timestamp, then pushing both the main tag and a branch-latest alias to the registry to complete the deployment tracking cycle.