CI/CD Pipeline Generator

Overview

Generate production-ready CI/CD pipeline configuration files for various platforms (GitHub Actions, GitLab CI, CircleCI, Jenkins). This skill provides templates and guidance for setting up automated workflows that handle linting, testing, building, and deployment for modern web applications, particularly Node.js/Next.js projects.

Core Capabilities

1. Platform Selection

Choose the appropriate CI/CD platform based on project requirements:

• - GitHub Actions: Best for GitHub-hosted projects with native integration
• GitLab CI/CD: Ideal for GitLab repositories with complex pipeline needs
• CircleCI: Optimized for Docker workflows and fast build times
• Jenkins: Suitable for self-hosted, highly customizable environments

Refer to references/platform-comparison.md for detailed platform comparisons, pros/cons, and use case recommendations.

2. Pipeline Configuration Generation

Generate pipeline configs following these principles:

Pipeline Stages

Structure pipelines with these standard stages:

1. 1. Install Dependencies

1. 2. Lint

1. 3. Test

1. 4. Build

1. 5. Deploy

Caching Strategy

Implement effective caching to speed up builds:

CODEBLOCK0

Environment Variables

Configure necessary environment variables:

• - NODE_ENV: Set to production for builds
• Platform-specific tokens: Store as secrets
• Build-time variables: Pass to build process

3. Template Usage

Use provided templates from assets/ directory:

GitHub Actions Template (assets/github-actions-nodejs.yml):

• - Multi-job workflow with lint, test, build, deploy
• Matrix builds for multiple Node.js versions (optional)
• Vercel deployment integration
• Artifact uploading
• Code coverage reporting

GitLab CI Template (assets/gitlab-ci-nodejs.yml):

• - Multi-stage pipeline
• Dependency caching
• Manual production deployment
• Automatic staging deployment
• Coverage reporting

To use a template:

1. 1. Copy the appropriate template file
2. Place in the correct location:

1. 3. Customize deployment targets, environment variables, and branch names
2. Add required secrets to platform settings

4. Deployment Configuration

Vercel Deployment

For GitHub Actions:
CODEBLOCK1

Required Secrets:

• - VERCEL_TOKEN: Get from Vercel account settings
• INLINECODE10: From Vercel project settings
• INLINECODE11: From Vercel project settings

Netlify Deployment

CODEBLOCK2

AWS S3 + CloudFront

CODEBLOCK3

5. Testing Integration

Configure test execution with proper reporting:

Jest Configuration:
CODEBLOCK4

Fail Fast Strategy:
CODEBLOCK5

6. Branch-Based Workflows

Implement different behaviors per branch:

Feature Branches / PRs:

• - Run lint + test only
• No deployment
• Add PR comments with test results

Develop Branch:

• - Run lint + test + build
• Deploy to staging environment
• Automatic deployment

Main Branch:

• - Run lint + test + build
• Deploy to production
• Manual approval (optional)
• Create release tags

Example:
CODEBLOCK6

Workflow Decision Tree

Follow this decision tree to generate the appropriate pipeline:

1. 1. Which platform?

1. 2. What stages are needed?

1. 3. Which deployment platform?

1. 4. What triggers?

1. 5. What environment variables needed?

Best Practices

Security

• - Store all secrets in platform secret management (never in code)
• Use least-privilege tokens (read-only when possible)
• Rotate secrets regularly
• Audit secret access permissions
• Never log secrets (use *** masking)

Performance

• - Cache dependencies aggressively
• Parallelize independent jobs
• Use matrix builds for multi-version testing
• Fail fast: Run quick checks before slow ones
• Optimize Docker layer caching

Reliability

• - Pin exact Node.js versions (18.x not just 18)
• Commit lockfiles (package-lock.json)
• Add retry logic for flaky external services
• Set reasonable timeouts (10-15 minutes max)
• Use continue-on-error for non-critical steps

Maintainability

• - Add comments explaining complex logic
• Use reusable workflows/templates
• Keep configs DRY (Don't Repeat Yourself)
• Version control all pipeline changes
• Document required secrets in README

Common Patterns

Multi-Environment Deployment

Matrix Testing

Conditional Steps

Artifact Management

Troubleshooting

Pipeline Failures

1. 1. Check action/job logs for error messages
2. Verify environment variables and secrets are set
3. Test commands locally before adding to pipeline
4. Check for platform-specific issues in documentation

Slow Builds

1. 1. Verify cache is working (check cache hit/miss logs)
2. Parallelize independent jobs
3. Use faster runners if available
4. Optimize dependency installation

Deployment Failures

1. 1. Verify deployment tokens are valid
2. Check platform status pages
3. Review deployment logs
4. Test deployment commands locally

Resources

Templates (assets/)

• - github-actions-nodejs.yml: Complete GitHub Actions workflow
• INLINECODE22: Complete GitLab CI pipeline

Reference Documentation (references/)

• - platform-comparison.md: Detailed comparison of CI/CD platforms, deployment targets, best practices, and common patterns

Example Usage

User Request: "Create a GitHub Actions workflow that runs tests and deploys to Vercel"

Steps:

1. 1. Copy assets/github-actions-nodejs.yml template
2. Create .github/workflows/ directory if it doesn't exist
3. Save as INLINECODE27
4. Update deployment section with Vercel credentials
5. Add secrets to GitHub repository settings:

1. 6. Commit and push to trigger workflow

User Request: "Set up GitLab CI with staging and production environments"

Steps:

1. 1. Copy assets/gitlab-ci-nodejs.yml template
2. Save as .gitlab-ci.yml in repository root
3. Configure GitLab CI/CD variables:

1. 4. Review manual approval settings for production
2. Commit to trigger pipeline

Advanced Configuration

Monorepo Support

Scheduled Runs

External Service Integration

Security Scanning