caching-strategy-optimizer — Claude Code skill
The caching-strategy-optimizer skill configures CI/CD caching for dependencies, Docker layers, build outputs, and test results. Use it when installs, builds, or tests slow down the pipeline.
MIT 272 installs ★ 64 updated 2026-01-12
npx skills add patricio0312rev/skills --skill caching-strategy-optimizer -a claude-codeWhat caching-strategy-optimizer does
The skill helps shape cache rules for npm, pnpm, Python pip, and Cargo. It also covers Docker layer caching with Buildx or a registry, plus caches for Next.js, Webpack, TypeScript, Jest, and Pytest. Cache keys use hashes from lock files or project files, while restore keys provide a fallback after smaller changes.
The included workflow patterns use actions/cache@v3, docker/setup-buildx-action@v3, and docker/build-push-action@v5. They also show how to log cache hits and compare pipeline timings before and after the change. GitHub Actions cache storage is limited to 10GB and expires after 7 days, so cache size and refresh behavior need a place in the design.
The skill is aimed at CI configurations where dependency, build, and test data need separate cache paths. Correct lock-file selection matters: a generic key can reuse the wrong data, while missing restore keys remove the fallback for minor edits.
What it helps with
- configure dependency caches for npm, pnpm, pip, or Cargo
- speed up Docker builds with layer caching
- store Next.js, Webpack, or TypeScript build caches
- cache Jest and Pytest results
- compare pipeline timing before and after caching
Example prompts for the agent
- Set up GitHub Actions caching for this project’s
package-lock.jsonand add suitablerestore-keys. - Add Docker layer caching with
docker/setup-buildx-action@v3anddocker/build-push-action@v5. - Inspect cache hits and produce a before-and-after comparison for dependency installation, builds, and tests.
How to install caching-strategy-optimizer
1Skills CLI (Vercel)
npx skills add patricio0312rev/skills --skill caching-strategy-optimizer -a claude-code2Manually: put the files in place
~/.claude/skills/caching-strategy-optimizer/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/caching-strategy-optimizer/
1Skills CLI (Vercel)
npx skills add patricio0312rev/skills --skill caching-strategy-optimizer -a codex2Manually: put the files in place
.agents/skills/caching-strategy-optimizer/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add patricio0312rev/skills --skill caching-strategy-optimizer -a cursor2Manually: put the files in place
.cursor/skills/caching-strategy-optimizer/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install patricio0312rev/skills ci-cd/caching-strategy-optimizer/SKILL.md2Manually: put the files in place
.github/skills/caching-strategy-optimizer/SKILL.md1Skills CLI (Vercel)
npx skills add patricio0312rev/skills --skill caching-strategy-optimizer -a gemini-cli2Platform CLI
gemini skills install https://github.com/patricio0312rev/skills --path ci-cd/caching-strategy-optimizerManually: put the files in place
.devin/skills/caching-strategy-optimizer/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add patricio0312rev/skills --skill caching-strategy-optimizer -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about caching-strategy-optimizer
How do I install caching-strategy-optimizer in Claude Code?
Run npx skills add patricio0312rev/skills --skill caching-strategy-optimizer -a claude-code, then check ~/.claude/skills/caching-strategy-optimizer/SKILL.md.
What does caching-strategy-optimizer do?
It helps configure CI/CD caches for dependencies, Docker layers, build outputs, and test results. It also covers cache-hit logging and before-and-after timing comparisons.
What should I account for in GitHub Actions cache design?
Tie keys to hashes of the relevant lock files and source files, then add restore keys for fallback matches. GitHub Actions cache storage has a 10GB limit and expires after 7 days.
Source text
SKILL.md · MIT
---
name: caching-strategy-optimizer
description: Optimizes CI/CD pipeline speed by implementing effective caching for dependencies, Docker layers, build outputs, and test results. Provides before/after performance metrics and best practices. Use for "CI caching", "pipeline optimization", "build speed", or "cache strategy".
---
# Caching Strategy Optimizer
Dramatically speed up CI pipelines with intelligent caching.
## Cache Key Strategy
### Package Manager Caches
```yaml
# NPM - Hash package-lock.json
- uses: actions/cache@v3
with:
path: ~/.npm
key: ${{ runner.os }}-npm-${{ hashFiles('**/package-lock.json') }}
restore-keys: |
${{ runner.os }}-npm-
# pnpm - More aggressive caching
- uses: pnpm/action-setup@v2
with:
version: 8
- uses: actions/cache@v3
with:
path: |
~/.pnpm-store
node_modules
key: ${{ runner.os }}-pnpm-${{ hashFiles('**/pnpm-lock.yaml') }}
restore-keys: |
${{ runner.os }}-pnpm-
# Python pip
- uses: actions/cache@v3
with:
path: ~/.cache/pip
key: ${{ runner.os }}-pip-${{ hashFiles('**/requirements.txt') }}
# Cargo/Rust
- uses: actions/cache@v3
with:
path: |
~/.cargo/bin/
~/.cargo/registry/index/
~/.cargo/registry/cache/
~/.cargo/git/db/
target/
key: ${{ runner.os }}-cargo-${{ hashFiles('**/Cargo.lock') }}
```
## Docker Layer Caching
### Using Buildx
```yaml
- name: Set up Docker Buildx
uses: docker/setup-buildx-action@v3
- name: Build with cache
uses: docker/build-push-action@v5
with:
context: .
cache-from: type=gha
cache-to: type=gha,mode=max
```
### Registry-based Cache
```yaml
- name: Build with registry cache
uses: docker/build-push-action@v5
with:
context: .
cache-from: type=registry,ref=myapp:buildcache
cache-to: type=registry,ref=myapp:buildcache,mode=max
```
## Build Output Caching
```yaml
# Next.js cache
- uses: actions/cache@v3
with:
path: |
${{ github.workspace }}/.next/cache
key: ${{ runner.os }}-nextjs-${{ hashFiles('**/package-lock.json') }}-${{ hashFiles('**/*.js', '**/*.jsx', '**/*.ts', '**/*.tsx') }}
restore-keys: |
${{ runner.os }}-nextjs-${{ hashFiles('**/package-lock.json') }}-
${{ runner.os }}-nextjs-
# Webpack cache
- uses: actions/cache@v3
with:
path: node_modules/.cache/webpack
key: ${{ runner.os }}-webpack-${{ hashFiles('webpack.config.js') }}-${{ hashFiles('src/**') }}
# TypeScript build cache
- uses: actions/cache@v3
with:
path: |
dist
tsconfig.tsbuildinfo
key: ${{ runner.os }}-tsc-${{ hashFiles('**/*.ts') }}
```
## Test Results Caching
```yaml
# Jest cache
- uses: actions/cache@v3
with:
path: /tmp/jest_rt
key: ${{ runner.os }}-jest-${{ hashFiles('**/*.test.ts') }}
# Pytest cache
- uses: actions/cache@v3
with:
path: .pytest_cache
key: ${{ runner.os }}-pytest-${{ hashFiles('**/*test*.py') }}
```
## Before/After Metrics
```markdown
## Before Optimization
- Total time: 12 minutes
- npm ci: 4 minutes
- Build: 5 minutes
- Tests: 3 minutes
## After Caching
- Total time: 3 minutes
- npm ci: 30 seconds (cache hit)
- Build: 1 minute (incremental)
- Tests: 1.5 minutes (cache hit)
**Improvement: 75% faster (12m → 3m)**
```
## Cache Hit Rate Monitoring
```yaml
- name: Check cache hit
id: cache
uses: actions/cache@v3
with:
path: node_modules
key: ${{ runner.os }}-deps-${{ hashFiles('package-lock.json') }}
- name: Log cache status
run: |
if [ "${{ steps.cache.outputs.cache-hit }}" == "true" ]; then
echo "✅ Cache hit - saved $(date -u -d @$SECONDS +%M:%S)"
else
echo "❌ Cache miss - installing from scratch"
fi
```
## Best Practices
1. **Precise keys**: Include all dependencies in hash
2. **Restore keys**: Fallback to partial matches
3. **Multiple paths**: Cache related files together
4. **Size limits**: GitHub Actions limit is 10GB
5. **Expiration**: Caches expire after 7 days
6. **Mode=max**: Docker cache mode for better hits
7. **Monitor hits**: Track cache effectiveness
## Common Pitfalls
❌ **Too generic keys**: `key: deps` (always hits)
✅ **Specific keys**: `key: deps-${{ hashFiles('package-lock.json') }}`
❌ **Missing restore-keys**: Cache miss on minor changes
✅ **Restore keys**: Partial match fallback
❌ **Caching node_modules with wrong lock file**
✅ **Match lock file**: Hash the right lockfile
## Output Checklist
- [ ] Package manager cache configured
- [ ] Build output cache
- [ ] Docker layer cache (if applicable)
- [ ] Test cache configured
- [ ] Cache keys use file hashes
- [ ] Restore keys for fallback
- [ ] Before/after metrics documented
- [ ] Cache hit monitoring
© patricio0312rev · MIT · patricio0312rev/skills