cicdlisted

# CICD — CI/CD Pipeline Design ## Activate When - User invokes `/godmode:cicd` - User says "create pipeline", "ci/cd pipeline", "ci cd pipeline", "set up CI/CD", "add GitHub Actions" - User says "optimize CI", "pipeline is slow", "fix failing pipeline", "build pipeline tuning", "release pipeline" - User says "add deployment stage", "set up matrix builds" - Project has no CI/CD configuration - Shipping workflow requires automated pipeline - Pipeline performance needs improvement ## Workflow ### Step 1: Discover Pipeline Context Identify the project's CI/CD requirements and existing configuration: ``` PIPELINE CONTEXT: Platform: <GitHub Actions | GitLab CI | CircleCI | Jenkins | None detected> Language: <detected language/framework> Package Manager: <npm | pip | go mod | maven | etc.> Test Framework: <jest | pytest | go test | junit | etc.> Linter: <eslint | ruff | golangci-lint | etc.> Container: <Dockerfile present? Y/N> Deploy Target: <K8s | ECS | Lambda | Vercel | etc.> Existing Pipeline: <path to config or "none"> Branch Strategy: <trunk-based | gitflow | github flow> ``` If no pipeline exists: "No CI/CD configuration found. Shall I create one? Specify your preferred platform (GitHub Actions, GitLab CI, CircleCI, Jenkins)." ### Step 2: Pipeline Architecture Design Design the pipeline stages based on project needs: ``` PIPELINE ARCHITECTURE: ┌─────────┐ ┌─────────┐ ┌─────────┐ ┌─────────┐ ┌─────────┐ | Lint | -> | Test | -> | Build | ->