skills.rest
hiromaily
hiromailyCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

verify-buildkit-cache

Verify BuildKit cache persistence and restoration in GitHub Actions CI logs.

126|41|Updated Aug 4, 2018
Search Tags:#github actions#go#docker#cache#ci#buildkit
One-click install
npx skills add https://github.com/hiromaily/go-crypto-wallet --skill verify-buildkit-cache
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verify-buildkit-cache
Source: https://github.com/hiromaily/go-crypto-wallet/tree/main/.claude/skills/verify-buildkit-cache
Command: npx skills add https://github.com/hiromaily/go-crypto-wallet --skill verify-buildkit-cache

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps CI/CD teams verify that Docker BuildKit cache mounts (GOMODCACHE and GOCACHE) persist across GitHub Actions jobs and are reinjected into subsequent steps, ensuring faster Go builds.

Core Features & Use Cases

  • Cache Persistence & Restoration: Verify that cache mounts persist across jobs and are restored by Actions.
  • Bottleneck Diagnosis: Detect when GOMODCACHE or GOCACHE are not preserved and identify slow build causes.
  • Use Case: When CI builds slow down due to cache misses, run this skill to confirm BuildKit cache flow works with buildkit-dance.

Quick Start

Run the verification against your CI logs to confirm that cache mounts were persisted, restored, and speed up builds.

Frequently Asked Questions about verify-buildkit-cache

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

FAQPage Schema
How do I verify BuildKit cache effectiveness from GitHub Actions logs?▼

To verify BuildKit cache effectiveness, analyze CI logs to check if cache mounts persist across jobs and are restored by Actions, confirming GOMODCACHE and GOCACHE utilization for faster Go builds.

Why does my Go build cache miss in Docker when using GitHub Actions?▼

Go build cache misses in Docker occur when GOMODCACHE or GOCACHE are not preserved across jobs. Analyze RUN --mount=type=cache usage and cache injection steps to diagnose the bottleneck.

How do I check if GOMODCACHE and GOCACHE persist across CI jobs?▼

Check if GOMODCACHE and GOCACHE persist across CI jobs by verifying cache mount restoration in logs and detecting cache injection or dance steps that reinject mounts into subsequent steps.

Does Docker BuildKit cache work with Go projects in GitHub Actions?▼

Docker BuildKit cache works with Go projects in GitHub Actions by using RUN --mount=type=cache to persist GOMODCACHE and GOCACHE, which Actions then restores to speed up subsequent builds.

What criteria determine if BuildKit cache is working in CI pipelines?▼

BuildKit cache effectiveness is determined by pass/fail criteria based on cache size and build times, verifying that cache mounts persist, are restored by Actions, and reduce build duration.

How do I diagnose slow Go builds caused by Docker BuildKit cache misses?▼

Diagnose slow Go builds by running verification against CI logs to confirm BuildKit cache flow works with buildkit-dance, detecting whether GOMODCACHE or GOCACHE are not preserved across jobs.

Related Skills

Explore More Software Engineering Skills→
kettleofketchupkettleofketchup

docker

Optimize Docker builds with layer ordering, BuildKit cache mounts, and multi-stage patterns.

Community
Advanced
sunny0826sunny0826
3

dockerfile-optimizer

Optimize Dockerfiles with multi-stage builds, minimal base images, and caching.

Community
Advanced
dotBeepsdotBeeps

docker

Optimize Dockerfiles and Compose configurations for smaller, secure images.

Community
Intermediate
freedomw1987freedomw1987
2

docker-build-cache-debug

Diagnose stale Docker build cache with timestamp comparisons and forced rebuilds.

Community
Intermediate