gen-ci

CI/CD Pipeline Generator

Generate production-quality CI/CD pipelines for: $ARGUMENTS

Parse $ARGUMENTS to determine:

• Platform: github-actions (default if not specified), gitlab-ci, or bitbucket
• Mode: --full flag means generate ALL pipeline files including Docker files, security scans, release automation, and deployment pipelines. Without --full, generate only the core CI pipeline (lint, test, build).

---

Step 1: Detect Project Stack

Run all detection tasks in parallel using Agent tool (mode = "bypassPermissions"). Scan the project root and subdirectories to build a complete technology profile.

1A: Detect Backend Stack

Search for these files and extract relevant information:

# Python detection
ls requirements.txt pyproject.toml setup.py setup.cfg Pipfile poetry.lock 2>/dev/null

# If Python found, detect framework
grep -l "fastapi\|FastAPI" requirements.txt pyproject.toml 2>/dev/null
grep -l "django\|Django" requirements.txt pyproject.toml 2>/dev/null
grep -l "flask\|Flask" requirements.txt pyproject.toml 2>/dev/null

# Node.js detection
ls package.json pnpm-lock.yaml yarn.lock package-lock.json bun.lockb 2>/dev/null

# Go detection
ls go.mod go.sum 2>/dev/null

# Rust detection
ls Cargo.toml Cargo.lock 2>/dev/null

# Java detection
ls pom.xml build.gradle build.gradle.kts 2>/dev/null

Record the Python version from pyproject.toml (requires-python) or .python-version file. Default to 3.11 and 3.12 for matrix testing.

Record the Node version from package.json (engines.node) or .nvmrc or .node-version. Default to 20 and 22 for matrix testing.

Record the Java version from build.gradle.kts (sourceCompatibility) or .java-version. Default to 21 for testing.

NestJS detection: If package.json contains @nestjs/core, this is a NestJS backend. Use pnpm commands and NestJS-specific CI steps (build, lint, test:e2e).

Spring Boot detection: If build.gradle.kts or pom.xml contains spring-boot, this is a Spring Boot backend. Use ./gradlew commands for build, test, and quality checks (checkstyle, spotbugs).