ci-cd-and-automation

1# CI/CD and Automation
2 
3## Overview
4 
5Automate quality gates so that no change reaches production without passing tests, lint, type checking, and build. CI/CD is the enforcement mechanism for every other skill — it catches what humans and agents miss, and it does so consistently on every single change.
6 
7**Shift Left:** Catch problems as early in the pipeline as possible. A bug caught in linting costs minutes; the same bug caught in production costs hours. Move checks upstream — static analysis before tests, tests before staging, staging before production.
8 
9**Faster is Safer:** Smaller batches and more frequent releases reduce risk, not increase it. A deployment with 3 changes is easier to debug than one with 30. Frequent releases build confidence in the release process itself.
10 
11## When to Use
12 
13- Setting up a new project's CI pipeline
14- Adding or modifying automated checks
15- Configuring deployment pipelines
16- When a change should trigger automated verification
17- Debugging CI failures
18 
19## The Quality Gate Pipeline
20 
21Every change goes through these gates before merge:
22 
23```
24Pull Request Opened
25    │
26    ▼
27┌─────────────────┐
28│   LINT CHECK     │  eslint, prettier
29│   ↓ pass         │
30│   TYPE CHECK     │  tsc --noEmit
31│   ↓ pass         │
32│   UNIT TESTS     │  jest/vitest
33│   ↓ pass         │
34│   BUILD          │  npm run build
35│   ↓ pass         │
36│   INTEGRATION    │  API/DB tests
37│   ↓ pass         │
38│   E2E (optional) │  Playwright/Cypress
39│   ↓ pass         │
40…