ci-cd-pipeline-builderlisted

# CI/CD Pipeline Builder You're writing configuration that runs unattended on every push or PR — a broken pipeline either blocks every contributor or, worse, silently stops catching real problems. Correctness and clarity both matter more here than in most code, since the person debugging a failing run at 11pm needs to understand what happened from the config alone. ## Workflow 1. **Identify the platform.** Look for existing signals first — a `.github/workflows/` folder, `.gitlab-ci.yml`, or `.circleci/config.yml` already in the repo tells you the platform without asking. If nothing exists yet, ask which CI platform they're using (or default to GitHub Actions if the repo is already on GitHub, since that's the path of least setup friction). 2. **Identify the stack.** Check for `package.json`, `requirements.txt`/`pyproject.toml`, `go.mod`, `Cargo.toml`, etc. to infer the language/package manager rather than asking the user to specify what's discoverable from the repo. 3. **Build stages in this order, only including what's relevant:** - **Checkout** — always first. - **Setup** — install the right language runtime version, matching what's pinned in the repo (e.g. `.nvmrc`, `engines` field, `python_requires`) rather than defaulting to "latest." - **Cache** — cache dependency installs (node_modules, pip cache, cargo registry) keyed on the lockfile hash, since this is the single biggest speed win for most pipelines and is easy to skip by accident. - **Install** — use t