Build GitLab CI/CD pipelines with multi-stage workflows, caching, and distributed runners for scalable automation. Use when implementing GitLab CI/CD, optimizing pipeline performance, or setting up automated testing and deployment.
90
82%
Does it follow best practices?
Impact
94%
1.18xAverage score across 6 eval scenarios
Advisory
Suggest reviewing before use
Node.js CI with Docker build and coverage
Pinned image tags
100%
100%
DOCKER_DRIVER variable
0%
100%
DOCKER_TLS_CERTDIR variable
50%
100%
npm ci usage
100%
100%
CI_COMMIT_REF_SLUG cache key
0%
100%
Artifacts expire_in set
100%
100%
Coverage regex
60%
100%
Cobertura coverage report
100%
100%
docker:24-dind service
100%
100%
Dual image tags
100%
100%
Cache pull-push policy
0%
100%
Pipeline stages defined
100%
100%
Multi-environment Kubernetes deployment pipeline
YAML anchor for template
100%
100%
bitnami/kubectl image
100%
100%
kubectl rollout status
100%
100%
Production manual gate
100%
100%
Staging environment block
100%
0%
Production environment block
100%
0%
Staging branch restriction
100%
100%
Production branch restriction
0%
100%
kubectl credential setup
100%
100%
Pinned non-kubectl image tags
100%
100%
Terraform pipeline with security scanning
SAST template included
0%
100%
Dependency-Scanning template
0%
100%
Container-Scanning template
100%
100%
trivy --exit-code 1
0%
100%
trivy HIGH,CRITICAL severity
0%
100%
aquasec/trivy image
0%
100%
allow_failure on scan job
0%
100%
Terraform stage order
100%
100%
TF_VERSION variable
100%
100%
hashicorp/terraform image
100%
100%
tfplan artifact saved
100%
100%
apply dependencies on plan
100%
100%
terraform fmt -check
0%
100%
TF_ROOT + before_script cd
100%
100%
Dynamic child pipeline generation
Generator job artifact
100%
100%
Trigger artifact reference
100%
100%
strategy: depend
100%
100%
Pinned image tags
100%
50%
Artifact expire_in
0%
0%
Stages defined
100%
100%
Generator job stage
100%
100%
Python script invoked
100%
100%
Per-job cache keys and merge request pipelines
Distinct per-job cache keys
100%
100%
Job-specific cache paths
100%
100%
Global cache with CI_COMMIT_REF_SLUG
0%
100%
Cache pull-push policy
100%
100%
Merge request pipeline support
100%
100%
Pinned image tags
100%
100%
Frontend and backend stages
100%
100%
Artifacts expire_in
0%
100%
Cache design documented
100%
100%
Pipeline schedules and CI/CD variables for secrets
Schedule-only job rule
100%
100%
No hardcoded credentials
100%
100%
CI/CD variable references for secrets
100%
100%
Merge request pipeline support
100%
100%
Unit tests run on normal pushes
100%
100%
Pinned image tags
100%
100%
Stages defined
100%
100%
pipeline-notes.md documents secrets
100%
100%
70444e5
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.