home / skills / enoch-robinson / agent-skill-collection / ci-cd-builder

ci-cd-builder skill

safe

This skill helps you quickly configure robust CI/CD pipelines across GitHub Actions, GitLab CI, and other tools for automated testing and deployment.

npx playbooks add skill enoch-robinson/agent-skill-collection --skill ci-cd-builder

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

2.4 KB

---
name: ci-cd-builder
description: CI/CD 流水线配置指南。当用户需要配置 GitHub Actions、GitLab CI、自动化测试、自动部署或持续集成/持续部署流程时使用此技能。
---

# CI/CD Builder

帮助开发者快速搭建高效的持续集成和持续部署流水线。

## 支持平台

- GitHub Actions（主要）
- GitLab CI/CD
- Jenkins
- CircleCI

## GitHub Actions 模板

### Node.js 项目

```yaml
name: CI/CD Pipeline

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

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

  build:
    needs: test
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version: '20'
          cache: 'npm'
      - run: npm ci
      - run: npm run build
      - uses: actions/upload-artifact@v4
        with:
          name: build
          path: dist/
```

### Docker 构建与推送

```yaml
  docker:
    needs: build
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: docker/setup-buildx-action@v3
      - uses: docker/login-action@v3
        with:
          registry: ghcr.io
          username: ${{ github.actor }}
          password: ${{ secrets.GITHUB_TOKEN }}
      - uses: docker/build-push-action@v5
        with:
          push: true
          tags: ghcr.io/${{ github.repository }}:${{ github.sha }}
```

##常用配置片段

### 缓存依赖

```yaml
- uses: actions/cache@v4
  with:
    path: ~/.npm
    key: ${{ runner.os }}-node-${{ hashFiles('**/package-lock.json') }}
```

### 条件执行

```yaml
- name: Deploy to Production
  if: github.ref == 'refs/heads/main'
  run: ./deploy.sh
```

### Secrets 使用

```yaml
env:
  API_KEY: ${{ secrets.API_KEY }}
  DATABASE_URL: ${{ secrets.DATABASE_URL }}
```

## 最佳实践

1. **快速反馈**：测试任务并行执行
2. **缓存优化**：缓存依赖减少构建时间
3. **安全存储**：敏感信息使用 Secrets
4. **版本锁定**：固定 Action 版本号
5. **失败通知**：配置 Slack/邮件通知

## 参考资源

- GitHub Actions 文档: https://docs.github.com/en/actions
- GitLab CI 文档: https://docs.gitlab.com/ee/ci/

Overview

This skill helps developers design and implement CI/CD pipelines for GitHub Actions, GitLab CI, Jenkins, and CircleCI. It provides ready-to-use templates, common configuration snippets, and practical deployment patterns for Node.js, Docker, testing, and artifact management. The goal is faster feedback, secure secret handling, and repeatable automated builds and deployments.

How this skill works

The skill inspects project type and recommends pipeline templates and steps tailored to that stack (for example Node.js test/build, Docker build-and-push). It supplies concrete YAML snippets for job orchestration, caching, conditional deployment, and secret injection. It also suggests pipeline structure: parallel test jobs, build artifacts, and dependent deployment jobs, plus notifications and version pinning.

When to use it

Setting up CI for a new repository (Node.js, Docker, or polyglot projects).
Adding automated tests, linting, and build stages to existing workflows.
Configuring Docker image build and push to a registry like GitHub Container Registry.
Implementing conditional production deploys and environment-specific steps.
Optimizing pipeline performance with dependency caching and parallel jobs.

Best practices

Split fast feedback (unit tests, lint) into parallel jobs to reduce latency.
Cache dependencies (npm, pip, etc.) to speed repeat builds and reduce flakiness.
Store credentials in platform Secrets and inject them as environment variables at runtime.
Pin Action and runner tool versions to avoid unexpected breaking changes.
Publish build artifacts from build jobs and gate deployments on successful tests and security scans.

Example use cases

Node.js project CI: checkout, setup-node, npm ci, run tests, lint, build, upload artifacts.
Docker pipeline: buildx build and push images to ghcr.io with credentials from secrets.
Conditional deploy: run deploy script only on main branch using an if condition.
Cache dependencies: use actions/cache to reuse npm cache keyed by package-lock.json hash.
Multi-stage pipeline: tests -> build -> docker push -> deploy, with notifications on failure.

FAQ

Which platforms does this cover?

Templates and guidance are provided for GitHub Actions, GitLab CI, Jenkins, and CircleCI, with primary examples for GitHub Actions.

How do I store and use secrets?

Add secrets in your CI/CD platform (e.g., GitHub Secrets) and reference them as environment variables in job steps to avoid exposing credentials.