building-ci-pipelines

Constructs CI/CD pipelines with SLSA provenance, caching, and parallelization for GitHub Actions, GitLab CI, and Argo Workflows.

1|Updated Feb 24, 2026

Search Tags:#ci/cd #caching #github actions #monorepo #gitlab ci #pipeline automation #slsa

One-click install

npx skills add https://github.com/masermediagroup-stack/maser-media --skill building-ci-pipelines-masermediagroup-stack

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: building-ci-pipelines
Source: https://github.com/masermediagroup-stack/maser-media/tree/main/.cursor/skills/community/ai-design-components/skills/building-ci-pipelines
Command: npx skills add https://github.com/masermediagroup-stack/maser-media --skill building-ci-pipelines-masermediagroup-stack

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyyaml, and includes scripts (resource) and references (resource) components.

What problem does it solve? Setting up CI/CD pipelines from scratch involves repetitive configuration, security pitfalls like leaked credentials, and slow builds that waste CI minutes. This Skill provides tested workflow patterns so you can ship secure, fast pipelines without reinventing them. ## Core Features & Use Cases - Multi-Platform Pipeline Patterns: Ready-to-use workflow templates for GitHub Actions, GitLab CI, Argo Workflows, and Jenkins covering lint, test, build, and deploy stages. - Supply Chain Security: SLSA Level 3 provenance generation, OIDC federation for credential-free cloud authentication, secret scanning, and SBOM generation. - Monorepo & Performance Optimization: Turborepo/Nx affected detection, multi-layer caching, matrix strategies, and test sharding that cut CI time by 60-90%. - Use Case: A team with a 50-package monorepo replaces a 15-minute build-everything pipeline with affected detection and remote caching, reducing CI runs to 4 minutes while adding SLSA provenance to release artifacts. ## Quick Start Ask the AI to set up a GitHub Actions CI pipeline with lint, test, and build jobs for your Node.js project, including dependency caching and SLSA provenance for releases.

Frequently Asked Questions about building-ci-pipelines

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

FAQPage Schema

How do I set up a CI pipeline in GitHub Actions?▼

Create a workflow file at .github/workflows/ci.yml with trigger events, jobs, and steps. A basic pipeline chains lint, test, and build jobs using the needs keyword so each stage runs only after the previous one passes.

How to speed up CI builds in a monorepo?▼

Use affected detection with Turborepo or Nx to build only packages changed since the base branch, plus their dependents. Combine this with remote caching to achieve 60-80% CI time reduction compared to building everything.

GitHub Actions vs GitLab CI for monorepos?▼

GitHub Actions offers native SLSA support, OIDC, and a large action marketplace, while GitLab CI provides parent-child pipelines and dynamic pipeline generation that suit monorepos well. GitLab rates excellent for monorepo support; GitHub Actions rates good.

Can GitHub Actions deploy to AWS without stored credentials?▼

Yes, use OIDC federation by granting id-token: write permission and calling aws-actions/configure-aws-credentials with a role ARN. This issues short-lived credentials with a one-hour lifetime and a full audit trail, eliminating stored secrets.

What is SLSA provenance and how do I generate it?▼

SLSA provenance is a signed record describing how an artifact was built, including the builder, source commit, and materials. Generate Level 3 provenance in GitHub Actions using the slsa-framework/slsa-github-generator reusable workflow, then verify it with cosign verify-attestation.

Why is my GitHub Actions cache hit rate low?▼

Low hit rates usually come from overly specific cache keys like github.sha that change every run. Use hash-based keys on lock files such as package-lock.json and provide restore-keys fallbacks so partial matches still restore dependencies.