ci-cd-and-automation

Create a workflow file at .github/workflows/ci.yml that triggers on pull requests and pushes to main. Add jobs that install dependencies with npm ci, then run lint, tsc --noEmit, tests with coverage, build, and npm audit in sequence.

Use the services key to spin up a PostgreSQL container with health checks, then run migrations and integration tests against it. Store the database password in GitHub Secrets rather than hardcoding credentials in the workflow file.

A complete pipeline runs lint, type checking, unit tests, build, integration tests, optional E2E tests, security audit, and bundle size checks. No gate should be skipped, and branch protection should block merges when any check fails.

Cache dependencies with the setup-node cache option, split lint, typecheck, and test into parallel jobs, use path filters to skip unrelated jobs, and shard test suites across runners. Apply these in order when the pipeline exceeds 10 minutes.

Use feature flags to merge incomplete features to main early while keeping them disabled in production. They enable canary rollouts, A/B tests, and instant rollback without redeploying, but flags should be removed after full rollout to avoid technical debt.

Copy the specific CI failure output and paste it to the agent with instructions to fix and verify locally before pushing. Lint failures map to npm run lint --fix, type errors to the reported location, and test failures to a debugging workflow.