Docker Build with Tracking

SkillCloud & infra

Build Docker images with proper tagging, cache busting, and build tracking. Prevents stale image issues.

Available today. Use it from your connected AI after setup.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use the Docker Build with Tracking skill

What this skill tells your AI

The instructions your AI receives, as published by thelobbi/claude in .claude/skills/docker-build/SKILL.md and read by ahel’s review.

Build a Docker image with proper tagging and tracking: $ARGUMENTS

Process

  1. Determine the image tag - Use git SHA or timestamp, NEVER use :latest alone

    GIT_SHA=$(git rev-parse --short HEAD)
    TIMESTAMP=$(date +%Y%m%d-%H%M%S)
    TAG="${GIT_SHA}-${TIMESTAMP}"
    
  2. Build with cache busting when needed

    • For production builds: docker build --no-cache --pull -t <registry>/<image>:${TAG} .
    • For dev builds: docker build -t <registry>/<image>:${TAG} .
    • Always also tag as :<branch>-latest for convenience
  3. Verify the build

    docker images | grep <image>
    docker inspect <registry>/<image>:${TAG} | jq '.[0].Created'
    
  4. Push to registry

    docker push <registry>/<image>:${TAG}
    docker push <registry>/<image>:<branch>-latest
    
  5. Verify in registry

    # For ACR:
    az acr repository show-tags --name <registry> --repository <image> --orderby time_desc --top 5
    # For Docker Hub:
    docker manifest inspect <registry>/<image>:${TAG}
    

Anti-Patterns (DO NOT)

  • Never build with just :latest tag
  • Never skip pushing after building
  • Never deploy without verifying the image exists in the registry
  • Never use imagePullPolicy: IfNotPresent with mutable tags

Signals

GitHub stars
21
Forks
2
Last commit
Sep 2026

ahel review

  • S4info
    community integration, published by thelobbi, not docker

Automated review, not a security audit. Ruleset v1+k2.

Advanced
Catalog kind
skill
Gateway key
docker-build
Source
github.com/thelobbi/claude