artifact-management
Manage build artifacts, Docker images, and package registries. Configure artifact repositories, versioning, and distribution strategies.
适合你,如果需要管理软件构建产物和容器镜像的版本与分发
npx oh-my-skill add aj-geddes/useful-ai-prompts/artifact-managementcurl -fsSL https://oh-my-skill.com/install.sh | bash -s -- aj-geddes/useful-ai-prompts/artifact-managementnpx oh-my-skill verify aj-geddes/useful-ai-prompts/artifact-management怎么用
商店整理自技能原文 · 版本 3f5182c · 表述以原文为准装上后,Claude 能帮你管理构建产物、Docker 镜像和软件包。它可以生成多阶段 Dockerfile、配置容器注册表、设置版本策略和保留规则,以及自动化发布流程。
当你需要处理 Docker 镜像、发布软件包、存储构建产物或优化容器层时触发。
技能原文 SKILL.md
Artifact Management
Table of Contents
- [Overview](#overview)
- [When to Use](#when-to-use)
- [Quick Start](#quick-start)
- [Reference Guides](#reference-guides)
- [Best Practices](#best-practices)
Overview
Implement comprehensive artifact management strategies for storing, versioning, and distributing built binaries, Docker images, and packages across environments.
When to Use
- Docker image registry management
- Package publication and versioning
- Build artifact storage and retrieval
- Container image optimization
- Artifact retention policies
- Multi-registry distribution
- Dependency caching
Quick Start
Minimal working example:
# Dockerfile with multi-stage build for optimization FROM node:18-alpine AS dependencies WORKDIR /app COPY package*.json ./ RUN npm ci --only=production FROM node:18-alpine AS builder WORKDIR /app COPY package*.json ./ RUN npm ci COPY . . RUN npm run build FROM node:18-alpine AS runtime WORKDIR /app COPY --from=dependencies /app/node_modules ./node_modules COPY --from=builder /app/dist ./dist COPY package*.json ./ EXPOSE 3000 HEALTHCHECK --interval=30s --timeout=3s --start-period=40s --retries=3 \ CMD node healthcheck.js CMD ["node", "dist/server.js"] // ... (see reference guides for full implementation)
Reference Guides
Detailed implementations in the references/ directory:
| Guide | Contents | |---|---| | [Docker Registry Configuration](references/docker-registry-configuration.md) | Docker Registry Configuration | | [GitHub Container Registry (GHCR) Push](references/github-container-registry-ghcr-push.md) | GitHub Container Registry (GHCR) Push | | [npm Package Publishing](references/npm-package-publishing.md) | npm Package Publishing, Artifact Retention Policy, Artifact Versioning, GitLab Package Registry |
Best Practices
✅ DO
- Use semantic versioning for artifacts
- Implement image scanning before deployment
- Set retention policies for old artifacts
- Use multi-stage builds for Docker images
- Sign and verify artifacts
- Implement artifact immutability
- Document artifact metadata
- Use specific base image versions
- Implement vulnerability scanning
- Cache layers aggressively
- Tag images with commit SHA
- Compress artifacts for storage
❌ DON'T
- Use
latesttag as sole identifier - Store secrets in artifacts
- Push artifacts without scanning
- Use untrusted base images
- Skip artifact verification
- Overwrite published artifacts
- Mix binary and source artifacts
- Ignore image layer optimization
- Store build logs with sensitive data