ci-cdlisted

# CI/CD and Automation Automate quality gates so 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 change. **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. A deployment with 3 changes is easier to debug than one with 30. ## When to use - Setting up a new project's CI pipeline. - Adding or modifying automated checks (lint, types, tests, build, audit). - Configuring deployment pipelines or deployment strategies. - Debugging CI failures. - When a change should trigger automated verification. **Not for:** debugging runtime bugs (use `debugging`); production launch strategy and rollback (use `shipping`); routine commits (use `git-workflow`). ## Steps ### 1. Define the quality gate pipeline Every change goes through these gates before merge — no gate can be skipped. If lint fails, fix lint (don't disable the rule). If a test fails, fix the code (don't skip the test). ``` Pull Request │ ▼ LINT → code style + static analysis TYPE CHECK → type safety (typed languages only) UNIT TESTS → behavior BUILD → artifact compiles / bundles INTEGRATION → API/DB tests against real deps E2E (opt.) → full user journeys in a browser/app SECURITY → dependency + secret scan │ ▼ Rea