/gaia-config-ci

What it does

/gaia-config-ci scaffolds or regenerates a CI/CD pipeline for your project. On first run, it detects your CI platform, selects a promotion chain preset, defines quality gates, configures secrets management, and generates the pipeline configuration file. With --regenerate, it refreshes previously generated workflow files while preserving your manual edits through a backup-or-merge flow.

When to use it

• You are setting up CI/CD for a new project.
• You changed your project configuration and need to regenerate the CI workflow files.
• You want to switch CI presets (solo, small-team, standard, enterprise).

Prerequisites

• No strict prerequisites for initial setup. For --regenerate, the CI files must have been previously generated by this command.

How to invoke

/gaia-config-ci
/gaia-config-ci --preset standard
/gaia-config-ci --regenerate

Non-interactive / YOLO entry

To run without conversational prompts (CI drivers, automated runs, headless agent dispatch), use one of these mechanisms:

• YOLO via argument: pass the literal token yolo at the end of the slash command, e.g. /gaia-config-ci yolo. The skill auto-selects the standard preset and auto-continues every interactive prompt that has a documented default.
• YOLO via env var: export GAIA_YOLO_FLAG=1 before invocation. Equivalent to the argument form; useful in scripted contexts that can't easily edit the slash-command line.
• Preset bypass: pass --preset <solo|small-team|standard|enterprise|custom> to skip the preset prompt while still walking the rest of the flow. Pair with GAIA_YOLO_FLAG=1 for a fully unattended run.
• Non-interactive guard (auto-rename only): auto-rename-migration.sh requires both --force and GAIA_MIGRATE_ALLOW_FORCE=1 under GAIA_NONINTERACTIVE=1. This is a security control on the rename pass — the main config-ci flow is unaffected.

What YOLO does NOT bypass: open-question retry prompts in the schema-violation loop. Genuine schema violations still require human input — the engine treats them as open-question indicators per SKILL.md §126. YOLO never auto-resolves schema errors blindly.

What it does step by step

1. Detect CI platform Scans for existing CI config files (.github/workflows/, .gitlab-ci.yml, etc.). Warns if found and offers merge or overwrite.
2. Select promotion chain preset Presents four presets (solo, small-team, standard, enterprise) plus custom. In YOLO mode, auto-selects standard.
3. Define pipeline Configures build, lint, test, coverage, and deploy gates for the selected CI platform.
4. Configure quality gates Defines pass/fail thresholds for coverage and test pass rate.
5. Configure secrets management Documents required secrets and environment-level separation.
6. Define deployment strategy Sets up staging (auto-deploy) and production (manual approval) pipelines.
7. Configure monitoring Adds pipeline failure notifications and status badge.
8. Generate pipeline config Writes the CI config file and validates its schema. If validation fails, enters a retry loop where you can correct violations and re-validate.
9. Generate output Writes the CI/CD setup document to .gaia/artifacts/test-artifacts/ci-setup.md.

Inputs

Outputs

Example session

> /gaia-config-ci --preset standard

Detecting CI platform...
  No existing CI config found.

Using preset: standard
  staging -> production (2 environments)

Generating pipeline...
  Build, lint, test, coverage gates configured.
  Secrets management documented.
  Deployment strategy: auto-deploy to staging, manual approval for production.

Pipeline written to .github/workflows/gaia-pre-merge.yml
CI setup documented at .gaia/artifacts/test-artifacts/ci-setup.md

What to run next

• /gaia-readiness-check -- validate implementation readiness now that CI is configured.
• /gaia-ci-edit -- fine-tune individual environments in the promotion chain.

Troubleshooting

Existing CI config found

The command detected existing CI files. Choose merge (combine), overwrite, or abort.

Schema validation failed

The generated CI config has violations. The command shows each violation and lets you correct and re-validate in a loop.

Promotion chain already exists

The CI configuration already has a promotion chain. Choose overwrite, skip, or redirect to /gaia-ci-edit.

Related commands