Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
aj-geddes avatar

Gitlab Cicd Pipeline

  • 588 installs
  • 305 repo stars
  • Updated March 4, 2026
  • aj-geddes/useful-ai-prompts

gitlab-cicd-pipeline is a Claude Code skill that designs GitLab .gitlab-ci.yml pipelines with lint, test, build, security, and deploy stages for developers automating repository delivery on GitLab Runner infrastructure.

About

gitlab-cicd-pipeline is a GitLab CI/CD authoring skill for creating .gitlab-ci.yml files with staged jobs, artifacts, caching, Docker integration, and deployment strategies on GitLab Runner infrastructure. It covers multi-stage pipelines spanning lint, test, build, security scanning, review environments, and production deploys, plus runner and container execution configuration. Developers reach for this skill when standing up CI for a GitLab repository, wiring Docker registry pushes, or adding Kubernetes deployment stages without hand-writing every job block from scratch.

  • Multi-stage pipeline pattern: lint → test → build → security → deploy-review → deploy-prod
  • Cache keys on `${CI_COMMIT_REF_SLUG}` for `node_modules/` and `.npm/`
  • GitLab Runner, Docker image execution, and registry integration guidance
  • Reference guides for complete pipeline config and runner setup under `references/`
  • Variables such as `DOCKER_DRIVER` and `FF_USE_FASTZIP` for faster container builds

Gitlab Cicd Pipeline by the numbers

  • 588 all-time installs (skills.sh)
  • Ranked #246 of 1,435 DevOps & CI/CD skills by installs in the Skillselion catalog
  • Security screen: HIGH risk (skills.sh audit)
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/aj-geddes/useful-ai-prompts --skill gitlab-cicd-pipeline

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs588
repo stars305
Security audit2 / 3 scanners passed
Last updatedMarch 4, 2026
Repositoryaj-geddes/useful-ai-prompts

How do you set up GitLab CI/CD pipeline stages?

Stand up a GitLab `.gitlab-ci.yml` with lint, test, build, security, and review/production deploy stages for a repo.

Who is it for?

Developers onboarding a GitLab repository who need a full lint-test-build-security-deploy pipeline with runner and Docker setup.

Skip if: GitHub Actions workflows, local-only test scripts without GitLab Runner, or application feature coding unrelated to CI configuration.

When should I use this skill?

A user asks to create or extend .gitlab-ci.yml with stages, jobs, artifacts, caching, Docker registry, or Kubernetes deploy steps.

What you get

.gitlab-ci.yml with staged jobs, artifacts, caching, Docker integration, and deployment configuration for GitLab Runners.

  • .gitlab-ci.yml
  • CI job and stage definitions

Files

SKILL.mdMarkdownGitHub ↗

GitLab CI/CD Pipeline

Table of Contents

Overview

Create comprehensive GitLab CI/CD pipelines that automate building, testing, and deployment using GitLab Runner infrastructure and container execution.

When to Use

  • GitLab repository CI/CD setup
  • Multi-stage build pipelines
  • Docker registry integration
  • Kubernetes deployment
  • Review app deployment
  • Cache optimization
  • Dependency management

Quick Start

Minimal working example:

# .gitlab-ci.yml
image: node:18-alpine

variables:
  DOCKER_DRIVER: overlay2
  FF_USE_FASTZIP: "true"

stages:
  - lint
  - test
  - build
  - security
  - deploy-review
  - deploy-prod

cache:
  key: ${CI_COMMIT_REF_SLUG}
  paths:
    - node_modules/
    - .npm/

lint:
  stage: lint
  script:
    - npm install
// ... (see reference guides for full implementation)

Reference Guides

Detailed implementations in the references/ directory:

GuideContents
Complete Pipeline ConfigurationComplete Pipeline Configuration
GitLab Runner ConfigurationGitLab Runner Configuration
Docker Layer Caching OptimizationDocker Layer Caching Optimization
Multi-Project PipelineMulti-Project Pipeline
Kubernetes DeploymentKubernetes Deployment, Performance Testing Stage, Release Pipeline with Semantic Versioning

Best Practices

✅ DO

  • Use stages to organize pipeline flow
  • Implement caching for dependencies
  • Use artifacts for test reports
  • Set appropriate cache keys
  • Implement conditional execution with only and except
  • Use needs: for job dependencies
  • Clean up artifacts with expire_in
  • Use Docker for consistent environments
  • Implement security scanning stages
  • Set resource limits for jobs
  • Use merge request pipelines

❌ DON'T

  • Run tests serially when parallelizable
  • Cache everything unnecessarily
  • Leave large artifacts indefinitely
  • Store secrets in configuration files
  • Run privileged Docker without necessity
  • Skip security scanning
  • Ignore pipeline failures
  • Use only: [main] without proper controls

Related skills

FAQ

What stages does gitlab-cicd-pipeline cover?

gitlab-cicd-pipeline designs .gitlab-ci.yml pipelines with lint, test, build, security, review, and production deploy stages, including artifacts, caching, and GitLab Runner job configuration.

Does gitlab-cicd-pipeline support Docker and Kubernetes deploys?

Yes. gitlab-cicd-pipeline configures Docker registry integration, container execution on GitLab Runners, and deployment strategies including Kubernetes targets within the CI/CD YAML.

Is Gitlab Cicd Pipeline safe to install?

skills.sh reports 2 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

DevOps & CI/CDdevopsintegrations

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.