CI Config Generator

---
name: ci-config-gen
description: |
  Trigger when the user asks to generate a CI config for a specific provider
  (GitHub Actions, GitLab CI, CircleCI, Buildkite, Jenkins). Phrases:
  "generate CI config", "set up pipeline", "write .gitlab-ci.yml",
  "CircleCI config", "Jenkinsfile".
allowed-tools:
  - Read
  - Write
  - Grep
  - Glob
---

# CI Config Generator

Produce a working, provider-idiomatic CI config file for the detected
project stack. Opinionated defaults, small surface area, cache-aware.

## Prerequisites

- Project stack is detectable from lockfile or manifest
- Target CI provider is known (ask if ambiguous)

## Steps

1. **Detect the stack.** Walk the repo root for signals:
   - `package.json` plus `pnpm-lock.yaml` / `yarn.lock` / `package-lock.json`
   - `pyproject.toml` / `requirements.txt` / `poetry.lock`
   - `go.mod`, `Cargo.toml`, `Gemfile`, `pom.xml`, `build.gradle`

2. **Pick the provider template.** Map provider to file path:
   - GitHub Actions: `.github/workflows/ci.yml`
   - GitLab: `.gitlab-ci.yml`
   - CircleCI: `.circleci/config.yml`
   - Buildkite: `.buildkite/pipeline.yml`
   - Jenkins: `Jenkinsfile`

3. **Emit a minimal pipeline.** Install, lint, typecheck, test, build.
   Example for GitHub Actions + pnpm:
   ```yaml
   name: CI
   on: [push, pull_request]
   concurrency:
     group: ${{ github.workflow }}-${{ github.ref }}
     cancel-in-progress: true
   jobs:
     test:
       runs-on: ubuntu-latest
       steps:
         - uses: actions/checkout@v4
         - uses: pnpm/action-setup@v4
         - uses: actions/setup-node@v4
           with: { node-version: 20, cache: pnpm }
         - run: pnpm install --frozen-lockfile
         - run: pnpm lint && pnpm typecheck && pnpm test
   ```

4. **Wire caching.** Every provider has a cache primitive. Use it for the
   lockfile-resolved dep dir. Skip bespoke cache keys until a real hit rate
   problem appears.

5. **Pin third-party actions / orbs / images** by major version. Never use
   `@main` or `:latest` in CI.

## Anti-patterns

- Monolithic single job that hides which step failed
- Copy-pasting a template from another stack without pruning unused steps
- Running e2e on every push; gate behind a label or cron

## Output

- Provider-specific YAML or Jenkinsfile at the canonical path
- Lint, typecheck, test, build jobs wired
- Cache + concurrency + version pinning in place