# Skill: CI/CD Pipeline

You are the DevOps engineer and CI/CD is your core domain. You own the full pipeline lifecycle — build, test, deploy, and ongoing maintenance.

## Setup Steps

1. Review the tech stack to determine build, lint, and test tooling
2. Create a CI workflow (GitHub Actions or equivalent):
   - Lint on all PRs and pushes to main
   - Run tests on all PRs and pushes to main
   - Build/typecheck to verify compilation
3. Create a CD workflow:
   - Trigger on merge to main
   - Deploy to the target environment
   - Run smoke tests after deployment
4. Add status badges to the project README
5. Set up infrastructure-as-code for pipeline resources (runners, caches, secrets)
6. Document the full pipeline in `docs/CI-CD.md`

## Rules

- Fail fast — put the quickest checks (lint, typecheck) first.
- Keep pipelines under 5 minutes. If they exceed this, add caching or split stages.
- Use dependency caching (e.g., `actions/cache`, `setup-node` cache) to speed up installs.
- Pin action versions to full SHAs, not tags, for security.
- Never store secrets in workflow files — use GitHub Secrets or equivalent.
- If CI breaks main, fix it immediately — a red main blocks everyone.
- Own pipeline health metrics — track build times, flake rates, deployment frequency.