pipeline-blueprint

Generates CI/CD pipeline templates for GitHub Actions and GitLab CI by project type.

4.6k|462|Updated Jun 21, 2025

Search Tags:#docker #gitLab CI #pipeline templates #ci/CD #GitHub actions #Deployment Automation #devOps

One-click install

npx skills add https://github.com/zebbern/claude-code-guide --skill pipeline-blueprint

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: pipeline-blueprint
Source: https://github.com/zebbern/claude-code-guide/tree/main/skills/pipeline-blueprint
Command: npx skills add https://github.com/zebbern/claude-code-guide --skill pipeline-blueprint

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Setting up CI/CD pipelines from scratch is time-consuming and error-prone, especially when choosing the right stages, caching strategies, and security practices for a specific project type. This Skill provides ready-to-adapt pipeline templates and best practices for GitHub Actions and GitLab CI.

Core Features & Use Cases

Project-Type Templates: Provides complete pipeline configurations for frontend, backend, library/package, fullstack, monorepo (Turborepo/Nx), and mobile (React Native/Flutter) projects.
Security & Best Practices: Enforces least-privilege permissions, pinned action versions, secret management, dependency scanning, and branch protection guidance.
Advanced Patterns: Covers reusable GitHub workflows, GitLab include templates, matrix builds, Docker image builds, caching strategies, and gated production deployments.
Use Case: A developer starting a new Python backend service asks for a CI setup and receives a GitHub Actions workflow with Postgres service containers, linting, test coverage, and Docker image publishing to GHCR.

Quick Start

Ask the assistant to generate a CI/CD pipeline for your project type, for example: set up a GitHub Actions pipeline for my React frontend with lint, test, build, and deployment stages.

Frequently Asked Questions about pipeline-blueprint

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

FAQPage Schema

How do I set up a GitHub Actions pipeline for a Node.js frontend?▼

Use a workflow with checkout, setup-node with npm caching, then run npm ci, lint, test, and build steps. Upload the dist folder as an artifact and add a separate deploy job gated to pushes on the main branch.

What is the difference between GitHub Actions and GitLab CI pipeline templates?▼

GitHub Actions uses workflow YAML files with jobs, steps, and marketplace actions, while GitLab CI uses stages, scripts, and include templates. Both support caching, matrix builds, service containers, and environment-gated deployments.

How do I cache dependencies in CI pipelines to speed up builds?▼

Cache dependency directories keyed by lockfiles: node_modules or ~/.npm for Node, ~/.cache/pip for Python, ~/go/pkg/mod for Go, and ~/.gradle or ~/.m2 for Java. GitHub Actions setup actions have built-in cache options.

Can I run CI jobs only for changed parts of a monorepo?▼

Yes. Use dorny/paths-filter in GitHub Actions to detect changed directories and conditionally run jobs, or use Turborepo with turbo run --filter='...[HEAD^]' to build only affected packages.

How do I secure secrets in CI/CD pipelines?▼

Store secrets in GitHub Secrets or GitLab CI Variables, never hardcode them in pipeline files. Prefer OIDC over long-lived credentials, use least-privilege token permissions, and restrict who can trigger production deployments.

Why should I pin action versions instead of using latest tags?▼

Pinning actions to exact versions or commit SHAs prevents unexpected breakage and supply-chain attacks from compromised upstream releases. Using latest tags makes builds non-reproducible and harder to audit.