Pipeline Blueprint
Provide CI/CD best practices and pipeline templates for GitHub Actions and GitLab CI...
Install
npx skills add zebbern/claude-code-guide --skill pipeline-blueprint -g -a claude-code -y- Repository
- zebbern/claude-code-guide4.7k
- Category
- Design
- Updated
- 4d ago
- License
- MIT
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
Provide CI/CD best practices and pipeline templates for GitHub Actions and GitLab CI, recommending configurations based on project type (frontend, backend, fullstack, library, monorepo, mobile). Trigger when users ask about setting up CI/CD, automating builds, improving pipelines, or mention keywords like GitHub Actions, GitLab CI, pipeline templates, or deployment automation.
CI/CD Configuration Best Practices
This skill provides CI/CD pipeline templates and best practices for GitHub Actions and GitLab CI. It recommends configurations based on project type, helping teams quickly set up reliable, secure, and efficient pipelines.
How to Use
When a user describes their project (language, framework, deployment target), recommend the most appropriate pipeline template below. Adapt stages, caching strategies, and deployment steps to match their stack.
General Best Practices
Pipeline Design Principles
- Fail fast: Run linting and unit tests before expensive integration or E2E tests.
- Cache aggressively: Cache dependency directories (
node_modules,.pip_cache,.m2,.gradle) to speed up builds. - Pin versions: Pin CI runner images, tool versions, and action versions to SHA or exact tags, never use
latest. - Least privilege: Use minimal permissions for tokens and credentials. Prefer OIDC over long-lived secrets where supported.
- Parallelize: Split test suites across parallel jobs. Use matrix builds for multi-version testing.
- Immutable artifacts: Build once, promote the same artifact through staging → production.
- Branch protection: Require CI to pass before merging. Use status checks on the default branch.
Security Checklist
- Never hardcode secrets in pipeline files; use the platform's secret management (GitHub Secrets / GitLab CI Variables).
- Audit third-party actions/images before use. Prefer official or verified sources.
- Enable dependency scanning (Dependabot, GitLab Dependency Scanning) and SAST where possible.
- Restrict who can trigger production deployments.
- Rotate secrets on a regular cadence.
Project Type Templates
1. Frontend (React / Vue / Angular / Static Sites)
Key stages: Install → Lint → Test → Build → Deploy
GitHub Actions
name: Frontend CI/CD
