CI/CD Pipeline

---
name: ci-cd-pipeline
description: |
  Creates CI/CD pipeline configuration for automated build, test, and deploy.
  IMPORTANT: Activate this skill whenever the user asks to "set up CI",
  "add GitHub Actions", "CI/CD pipeline", or "automate deployment".
  This skill MUST be used for all CI/CD setup requests.
---

# CI/CD Pipeline

Sets up a complete CI/CD pipeline using GitHub Actions (or GitLab CI) based on your project's actual build scripts, test commands, and deployment target.

**Trigger:**

Say any of these to activate this skill:
- "set up CI"
- "add GitHub Actions"
- "create a CI/CD pipeline"
- "Use skill: ci cd pipeline"

**How It Works:**

1. Read package.json scripts to identify: build, test, lint, type-check commands
2. Check for existing CI config (.github/workflows, .gitlab-ci.yml) to extend rather than replace
3. Detect the deployment target (Vercel, Netlify, AWS, Railway, fly.io, etc.)
4. Create workflow file(s) with stages: install, lint, type-check, test, build, deploy
5. Set up proper caching for node_modules and build artifacts
6. Configure branch rules (run tests on PR, deploy on merge to main)
7. Add required environment variables as secrets references
8. Include status badges for the README

**Guidelines:**

- Use the project's actual scripts (npm run build, npm test) not custom commands
- Cache dependencies properly to speed up runs
- Fail fast: lint and type-check before running expensive tests
- Use matrix builds only if the project needs to test multiple Node versions
- Keep the pipeline under 10 minutes total

**Works With:**

- Best with: Claude Code CLI (can create workflow files and test locally with act)
- Also works: Cursor, Windsurf
- Expects: A project with build and test scripts defined

**Output Format:**

- GitHub Actions workflow file(s) in .github/workflows/
- Environment variables documented as comments in the workflow
- README badge snippet