CI CD Pipeline

CI/CD Pipeline

Mode Detection

• Repo mode — templates in tooling/ci/. Scaffold or modify pipeline configs.
• Chat mode — user pastes pipeline config or failure logs. Diagnose and provide corrected config.

Pipeline Design Principles

1. Fast feedback — lint and test before build; build before deploy
2. Fail fast — stop the pipeline at the first failure
3. Secrets via secret store — never hardcode credentials
4. Idempotent deploys — running the same deploy twice should be safe
5. Gate production — require passing tests before any production deploy

Standard Pipeline Stages

lint → test → build → push image → deploy staging → smoke test → deploy production

GitHub Actions

Debugging failures

# Enable debug logging by setting repository secret:
ACTIONS_STEP_DEBUG = true
ACTIONS_RUNNER_DEBUG = true

Common issues:

Useful patterns

# Run only on main branch
on:
  push:
    branches: [main]

# Matrix builds
strategy:
  matrix:
    node-version: [18, 20, 22]

# Reuse secrets
env:
  DATABASE_URL: ${{ secrets.DATABASE_URL }}

GitLab CI

Common issues:

Jenkins

Common issues:

Tooling Templates

• tooling/ci/github-actions/ — reusable workflow templates
• tooling/ci/gitlab-ci/ — .gitlab-ci.yml templates
• tooling/ci/jenkins/ — Jenkinsfile templates
• tooling/ci/starters/ — full CI/CD setups by stack

Source: tspry/superpowers-devops — distributed by TomeVault.