ci-cd-pipeline-builderlisted

# CI/CD Pipeline Builder ## What You Get - GitHub Actions or GitLab CI YAML file ready to commit - Dependency caching, pinned versions, test + lint + build stages ## Philosophy Start with a minimal reliable pipeline that runs tests on every push. Add complexity only when justified. A pipeline that is fast and trustworthy is better than one that is comprehensive and flaky. ## Workflow: 5 Phases ### Phase 1: Detect Stack Scan the repository for manifests, lockfiles, and configuration files. See [stack-detection.md](stack-detection.md) for the full signal table. Identify: - Primary language(s) and runtime versions - Package manager and lockfile - Test framework and test command - Linter and formatter - Build tool and build command - Monorepo structure (if applicable) ### Phase 2: Choose Platform Default to GitHub Actions unless the project already uses GitLab CI or the user requests otherwise. Check for existing pipeline files: - `.github/workflows/*.yml` -- GitHub Actions - `.gitlab-ci.yml` -- GitLab CI If a pipeline already exists, extend it rather than replacing it. ### Phase 3: Generate Pipeline Start with the minimal reliable baseline from [pipeline-templates.md](pipeline-templates.md): 1. Install dependencies (with caching) 2. Run linter/formatter check 3. Run tests 4. Build (if applicable) Use the detected runtime version. Pin action versions to specific SHAs or major versions. Use lockfile-based caching. ### Phase 4: Validate Before presenting the pipeline