github-actions-cicdlisted

# Purpose Author, review, and debug the GitHub Actions workflows that drive the project's repositories. Produce workflow YAML that matches the established CI job graph, the AWS ECR/ECS deploy contract, and the standardized workflow set each repo ships — so a workflow in any repo is recognizable from any other. Read the project's shape from `project.json` (repos/monorepo) — this skill covers both; the examples below use a multi-repo layout. Each repository owns its own `.github/workflows/` directory and runs the **same standardized set** of workflows. The application repos (e.g. the API repo — `project.json` → `mainApp` — a NestJS service, plus the client/admin/vendor/mobile repos) build container images; the infrastructure repo carries its own `ci.yml` + `deploy.yml`. Cloud is **AWS** — images go to ECR, services run on ECS with a rolling, force-new-deployment update. There is **no GCP, no Kubernetes, no Helm, and no GitOps controller** anywhere in this pipeline. Deploys are imperative `aws ecs update-service` calls followed by a stability poll. # When to use - Adding or modifying a job in a repo's `ci.yml` (type-check, lint, test, build, security, summary). - Writing or fixing the ECR build/push + ECS force-new-deployment flow in `deploy-prod.yml`. - Bringing a repo's workflow set in line with the standard (`ci.yml`, `deploy-prod.yml`, `nightly.yml`, `version-bump.yml`, `secret-scan.yml`, `dependabot-lockfix.yml`, `branch-protection.yml`). - Debugging a failing Actions