/deploy — CI/CD Management

/deploy — CI/CD Management

Create and manage CI/CD pipelines.

Detect Existing Pipeline

ls .github/workflows/ 2>/dev/null
ls .gitlab-ci.yml 2>/dev/null
ls .circleci/config.yml 2>/dev/null

Process

Creating a New Pipeline

Gather requirements via a single AskUserQuestion call (three questions in one questions array — not plain prose) so the user picks structured options instead of free-typing:

• CI provider — GitHub Actions · GitLab CI · CircleCI · Other
• Stages (multi-select) — lint · test · build · deploy · security scan
• Environments — staging · production · both

End your turn at the AskUserQuestion call. Wait for the answers before generating any pipeline template. If provider is "Other", follow up for the specific tool.

Once answered, present the one-shot plan — provider, stages, environments, and the exact file(s) to be written (e.g. .github/workflows/ci.yml) — and gate it with AskUserQuestion (not a bare sentence). Frame it "Pipeline plan ready — write it?" with options:

• Approve — write the workflow file(s) as planned
• Revise — adjust stages / environments (they describe the change)
• Change scope — different provider or file layout

End your turn at the AskUserQuestion call. Act on the selection; treat any free-form "looks good / approved / yes" as Approve. Write the workflow file only on Approve — this is the write gate; do not weaken it.

GitHub Actions Template

# .github/workflows/ci.yml
name: CI

on:
  push:
    branches: [main, develop]
  pull_request:
    branches: [main]

permissions:
  contents: read

jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - name: Setup runtime
        uses: actions/setup-node@v4
        with:
          node-version: '20'
          cache: 'npm'
      - run: npm ci
      - run: npm run lint
      - run: npm test
      - run: npm run build

  security:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - name: Security scan
        # magician-scan is provided by the magician plugin (on PATH when the
        # plugin is enabled). Make it optional so the job degrades gracefully
        # in repos where the binary is not installed.
        run: command -v magician-scan >/dev/null 2>&1 && magician-scan . || echo "magician-scan not present, skipping"

GitLab CI Template

# .gitlab-ci.yml
stages: [lint, test, build, security]

lint:
  stage: lint
  script: [npm run lint]

test:
  stage: test
  script: [npm test]

build:
  stage: build
  script: [npm run build]
  artifacts:
    paths: [dist/]

security:
  stage: security
  # magician-scan is provided by the magician plugin (on PATH when the plugin
  # is enabled). Optional — degrades gracefully if the binary is not present.
  script:
    - command -v magician-scan >/dev/null 2>&1 && magician-scan . || echo "magician-scan not present, skipping"

Monitoring a Pipeline

Prefer the Monitor tool — run the pipeline watcher in the background so each status change streams back as an event and you react the moment a job fails, without a blocking --watch holding the turn.

# GitHub Actions
gh run list --limit 5
gh run view <run-id>
gh run watch <run-id>   # run via the Monitor tool; falls back to a blocking watch pre-v2.1.98

For an unattended "until green" wait, pair with /goal, or schedule with /loop (self-paces when the interval is omitted; fixed-interval on Bedrock/Vertex).

Fixing a Failed Pipeline (loop until green)

1. Read the failure: gh run view <id> --log-failed
2. Fix the underlying issue
3. Push the fix
4. Monitor via the Monitor tool: gh run watch — on failure, repeat from step 1 until the run is green.

Autonomy — approve the plan, then run

After the requirements answers (the three questions — provider, stages, environments — plus the one-shot create plan), execute the remaining phases autonomously: detecting existing pipelines (ls), generating the template, and monitoring (gh run list/view/watch, --log-failed), plus kg query/blast and read-only git NEVER pause for permission. Re-gate only on this skill's real side effects: Write/Edit of the workflow file, git add/commit/push, and PR create. Do not weaken the write gate above. Doctrine: lore/autonomy.md.

Completion Signal

"Deploy pipeline configured. Monitor at: ."