ci-cd-pipeline-builder

一行命令安装

下载这个 Skill 需要先登录（免费注册，只需用户名和密码）。去登录 →

使用反馈 · 0

用过的同学可以在这里说说效果、坑点或改进建议，也可以直接提出新需求。

规范度体检 · 94/100

按元信息、示例、可执行性、完整性等 13 项自动检查，供作者自查改进；不影响用户评分。

• ✓ front-matter 含 name / description 15/15
• ✓ description 信息量（≥30 字） 5/5
• ✓ description 含使用场景语境 5/5
• ✓ version 字段 3/3
• ✓ license 字段 2/2
• ✓ 正文篇幅（≥300 字） 10/10
• ✓ 含代码块 / 命令示例 10/10
• ✓ 结构化步骤 / 清单（≥3 条） 8/8
• ✗ 有边界 / 限制说明 0/6
  没写什么时候不该用，容易被误触发
• ✓ 有输出格式 / 验收标准 6/6
• ✓ 引用的文件均存在 18/18
• ✓ SKILL.md 体积合理 6/6
• ✓ 整体体积可控（≤2MB） 6/6

版本历史

• v1.0.0 · 当前版本 2026-10-20

SKILL.md 内容

# CI/CD Pipeline Builder

**Tier:** POWERFUL  
**Category:** Engineering  
**Domain:** DevOps / Automation

## Overview

Use this skill to generate pragmatic CI/CD pipelines from detected project stack signals, not guesswork. It focuses on fast baseline generation, repeatable checks, and environment-aware deployment stages.

## Core Capabilities

- Detect language/runtime/tooling from repository files
- Recommend CI stages (`lint`, `test`, `build`, `deploy`)
- Generate GitHub Actions or GitLab CI starter pipelines
- Include caching and matrix strategy based on detected stack
- Emit machine-readable detection output for automation
- Keep pipeline logic aligned with project lockfiles and build commands

## When to Use

- Bootstrapping CI for a new repository
- Replacing brittle copied pipeline files
- Migrating between GitHub Actions and GitLab CI
- Auditing whether pipeline steps match actual stack
- Creating a reproducible baseline before custom hardening

## Key Workflows

### 1. Detect Stack

```bash
python3 scripts/stack_detector.py --repo . --format text
python3 scripts/stack_detector.py --repo . --format json > detected-stack.json
```

Supports input via stdin or `--input` file for offline analysis payloads.

### 2. Generate Pipeline From Detection

```bash
python3 scripts/pipeline_generator.py \
  --input detected-stack.json \
  --platform github \
  --output .github/workflows/ci.yml \
  --format text
```

Or end-to-end from repo directly:

```bash
python3 scripts/pipeline_generator.py --repo . --platform gitlab --output .gitlab-ci.yml
```

### 3. Validate Before Merge

1. Confirm commands exist in project (`test`, `lint`, `build`).
2. Run generated pipeline locally where possible.
3. Ensure required secrets/env vars are documented.
4. Keep deploy jobs gated by protected branches/environments.

### 4. Add Deployment Stages Safely

- Start with CI-only (`lint/test/build`).
- Add staging deploy with explicit environment context.
- Add production deploy with manual gate/approval.
- Keep rollout/rollback commands explicit and auditable.

## Script Interfaces

- `python3 scripts/stack_detector.py --help`
  - Detects stack signals from repository files
  - Reads optional JSON input from stdin/`--input`
- `python3 scripts/pipeline_generator.py --help`
  - Generates GitHub/GitLab YAML from detection payload
  - Writes to stdout or `--output`

## References

- [references/pipeline-design-notes.md](references/pipeline-design-notes.md) — common pitfalls, best practices, detection heuristics, generation strategy, platform decision notes, pre-merge validation checklist, and scaling guidance
- [references/github-actions-templates.md](references/github-actions-templates.md)
- [references/gitlab-ci-templates.md](references/gitlab-ci-templates.md)
- [references/deployment-gates.md](references/deployment-gates.md)
- [README.md](README.md)