Agent skill · software engineering · thebushidocollective

gitlab-ci-best-practices

Use when optimizing GitLab CI/CD pipelines for performance, reliability, or maintainability. Covers pipeline optimization and organizational patterns.

Why this skill is useful

Provides specific GitLab CI/CD optimization patterns and configurations that the AI wouldn't reliably generate on its own.

What it needs

About 2k tokens when loaded. Last updated 2026-07-19. 187 stars on the source repository.

What this skill does

GitLab CI - Best Practices Optimize GitLab CI/CD pipelines for performance, reliability, and maintainability. Pipeline Optimization Use DAG with Needs Parallel Execution Interruptible Jobs Configuration Organization Split Configuration Files Reusable Templates Extends Keyword Resource Management Resource Groups Runner Tags Error Handling Retry Configuration Allow Failure Security Best Practices Protected Pipelines Secure Variables Monitoring & Debugging Job Logging Pipeline Badges Common Anti-Patterns 1. Avoid: Running all jobs in sequence Do: Use needs for parallel execution 2. Avoid: Downloading all artifacts Do: Use dependencies to limit downloads 3. Avoid: Rebuilding nodemodules every job Do: Use cache with lock file keys 4. Avoid: Hardcoded secrets Do: Use CI/CD variables with protection 5. Avoid: Single monolithic .gitlab-ci.yml Do: Split into multiple included files

How to use it

Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:

@skills thebushidocollective/cicd-best-practices

View the source on GitHub

Browse the @skills marketplace