ci-cd-pipeline-builder

---
name: ci-cd-pipeline-builder
description: Use when bootstrapping CI, refactoring pipelines, or standardizing deployment workflows across repos from detected project stack.
category: Engineering
version: 1.0.0
tools: []
---

# CI/CD Pipeline Builder

Generate pragmatic pipelines from detected project stack signals. Focus on fast baseline generation, repeatable checks, and environment-aware deployment stages.

## Core Capabilities

- Detect language/runtime/tooling from repository files
- Recommend CI stages: lint, test, build, deploy
- Generate GitHub Actions or GitLab CI starter pipelines
- Include caching and matrix strategy based on stack
- Emit machine-readable detection output
- Align pipeline logic with lockfiles and build commands

## When to Use

- Bootstrapping CI for new repository
- Replacing brittle copied pipeline files
- Migrating between GitHub Actions and GitLab CI
- Auditing whether pipeline steps match actual stack
- Creating reproducible baseline before custom hardening

## Key Workflows

### 1. Detect Stack

```bash
python3 scripts/stack_detector.py --repo . --format text
python3 scripts/stack_detector.py --repo . --format json > detected-stack.json
```

Supports stdin or --input file for offline analysis.

### 2. Generate Pipeline From Detection

```bash
python3 scripts/pipeline_generator.py \
  --input detected-stack.json \
  --platform github \
  --output .github/workflows/ci.yml
```

Or end-to-end from repo:

```bash
python3 scripts/pipeline_generator.py --repo . --platform gitlab --output .gitlab-ci.yml
```

### 3. Validate Before Merge

1. Confirm commands exist: test, lint, build
2. Run generated pipeline locally where possible
3. Ensure required secrets/env vars are documented
4. Keep deploy jobs gated by protected branches

### 4. Add Deployment Stages Safely

- Start with CI-only (lint/test/build)
- Add staging deploy with explicit environment context
- Add production deploy with manual gate/approval
- Keep rollout/rollback commands explicit and auditable

## Script Interfaces

- stack_detector.py: Detect stack signals; read optional JSON from stdin/--input
- pipeline_generator.py: Generate GitHub/GitLab YAML from detection payload; write stdout or --output

## Best Practices

1. Confirm detection matches actual project
2. Test generated YAML before commit
3. Document all required secrets
4. Use matrix strategy for multi-version testing
5. Cache dependencies between runs
6. Gate production deployments with approval
7. Keep rollback procedures explicit