Gitlab ci
A comprehensive skill catalog for AI agents
npx -y skills add G1Joshi/Agent-Skills --skill gitlab-ciAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 10 stars10 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
GitLab CI/CD pipelines with runners and stages. Use for GitLab automation.
SKILL.md
1.7 KB, as published. Nobody here has run it
GitLab CI/CD
GitLab CI/CD is known for its robust pipeline definition (.gitlab-ci.yml) and Auto DevOps capabilities. In 2025, CI Components replace legacy templates for modular pipeline composition.
When to Use
- GitLab Users: It's integrated and excellent.
- Complex Pipelines: The DAG (Directed Acyclic Graph) capabilities are sophisticated (
needskeyword). - On-Prem: Excellent support for air-gapped instances.
Quick Start
# .gitlab-ci.yml
stages:
- build
- test
build-job:
stage: build
image: node:20
script:
- npm ci
- npm run build
artifacts:
paths:
- dist/
test-job:
stage: test
image: node:20
script:
- npm test
needs: [build-job]
Core Concepts
.gitlab-ci.yml
The heart of the pipeline. Defines stages, jobs, and environment variables.
Runners
The agents that run jobs. Unique feature: Docker-in-Docker support is first-class (using services: docker:dind).
CI Components (2025)
Reusable pipeline parts listed in the CI Catalog. Replaces the old include: template method with versioned, input-driven components.
Best Practices (2025)
Do:
- Use CI Components: Adopt the module catalog.
- Use
rules: Control when jobs run (e.g., only on Merge Requests, or only whenpackage.jsonchanges). - Use
cachevsartifacts: Usecachefor dependencies (node_modules) andartifactsfor output binaries passed between stages.
Don't:
- Don't use
only/except: They are deprecated. Userules.