CI/CD Pipeline Builder

Generate pragmatic CI/CD pipelines from detected project stack signals — fast baseline generation, repeatable checks, environment-aware deployment stages.

How to use it

Claude Code

Run the line below. It pulls the whole folder into ~/.claude/skills/ci-cd-pipeline-builder, including the files SKILL.md points to.
Describe your job in plain words. Claude Code follows the skill from there.

Claude Code — installs the whole folder, not just SKILL.md

npx degit alirezarezvani/claude-skills/engineering/skills/ci-cd-pipeline-builder#main ~/.claude/skills/ci-cd-pipeline-builder

For one project only, change the path to .claude/skills/ci-cd-pipeline-builder. This skill also uses detected-stack.json — copying SKILL.md alone won't be enough. See the folder on GitHub.

Claude (web or desktop app)

On this page open ⋯ → Download .md.
Save it as SKILL.md in a folder, zip the folder, then Customize → Skills → + → Create skill → Upload a skill.
Pick the file and Save. Claude shows the name and description and runs a security scan.
Check the skill is switched on.
Start a new chat and describe your job in plain words. The AI follows the skill from there.

ChatGPT or another app

ChatGPT: make a Project and paste it into Instructions.
Neither? Paste it at the top of a new chat — it works for that chat.

Not working?

Check which app you pasted it into — the steps above name the right one.
Some skills need the paid tier of Claude or ChatGPT.

Step-by-step guide with screenshots · Ask in the forum

Paste into Claude, ChatGPT or Cursor.

Show the full text90 lines

ci-cd-pipeline-builder/SKILL.md90 lines · 3.2 KB

PreviewCode

Outline

RawView on GitHub

name	description
ci-cd-pipeline-builder	Generate pragmatic CI/CD pipelines from detected project stack signals — fast baseline generation, repeatable checks, environment-aware deployment stages. Use when setting up CI for a new project, refactoring existing pipelines, or standardizing deployment workflows across multiple repos.

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

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

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:

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

3. Validate Before Merge

Confirm commands exist in project (test, lint, build).
Run generated pipeline locally where possible.
Ensure required secrets/env vars are documented.
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 — common pitfalls, best practices, detection heuristics, generation strategy, platform decision notes, pre-merge validation checklist, and scaling guidance
references/github-actions-templates.md
references/gitlab-ci-templates.md
references/deployment-gates.md
README.md

1	---
2	name: "ci-cd-pipeline-builder"
3	description: "Generate pragmatic CI/CD pipelines from detected project stack signals — fast baseline generation, repeatable checks, environment-aware deployment stages. Use when setting up CI for a new project, refactoring existing pipelines, or standardizing deployment workflows across multiple repos."
4	---
5
6	# CI/CD Pipeline Builder
7
8	Tier: POWERFUL
9	Category: Engineering
10	Domain: DevOps / Automation
11
12	## Overview
13
14	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.
15
16	## Core Capabilities
17
18	- Detect language/runtime/tooling from repository files
19	- Recommend CI stages (`lint`, `test`, `build`, `deploy`)
20	- Generate GitHub Actions or GitLab CI starter pipelines
21	- Include caching and matrix strategy based on detected stack
22	- Emit machine-readable detection output for automation
23	- Keep pipeline logic aligned with project lockfiles and build commands
24
25	## When to Use
26
27	- Bootstrapping CI for a new repository
28	- Replacing brittle copied pipeline files
29	- Migrating between GitHub Actions and GitLab CI
30	- Auditing whether pipeline steps match actual stack
31	- Creating a reproducible baseline before custom hardening
32
33	## Key Workflows
34
35	### 1. Detect Stack
36
37	```bash
38	python3 scripts/stack_detector.py --repo . --format text
39	python3 scripts/stack_detector.py --repo . --format json > detected-stack.json
40	```
41
42	Supports input via stdin or `--input` file for offline analysis payloads.
43
44	### 2. Generate Pipeline From Detection
45
46	```bash
47	python3 scripts/pipeline_generator.py \
48	--input detected-stack.json \
49	--platform github \
50	--output .github/workflows/ci.yml \
51	--format text
52	```
53
54	Or end-to-end from repo directly:
55
56	```bash
57	python3 scripts/pipeline_generator.py --repo . --platform gitlab --output .gitlab-ci.yml
58	```
59
60	### 3. Validate Before Merge
61
62	1. Confirm commands exist in project (`test`, `lint`, `build`).
63	2. Run generated pipeline locally where possible.
64	3. Ensure required secrets/env vars are documented.
65	4. Keep deploy jobs gated by protected branches/environments.
66
67	### 4. Add Deployment Stages Safely
68
69	- Start with CI-only (`lint/test/build`).
70	- Add staging deploy with explicit environment context.
71	- Add production deploy with manual gate/approval.
72	- Keep rollout/rollback commands explicit and auditable.
73
74	## Script Interfaces
75
76	- `python3 scripts/stack_detector.py --help`
77	- Detects stack signals from repository files
78	- Reads optional JSON input from stdin/`--input`
79	- `python3 scripts/pipeline_generator.py --help`
80	- Generates GitHub/GitLab YAML from detection payload
81	- Writes to stdout or `--output`
82
83	## References
84
85	- [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
86	- [references/github-actions-templates.md](references/github-actions-templates.md)
87	- [references/gitlab-ci-templates.md](references/gitlab-ci-templates.md)
88	- [references/deployment-gates.md](references/deployment-gates.md)
89	- [README.md](README.md)
90

Discussion

Alternatives

Also in CI/CD & releasesSee all 533 in Development →

CI/CD and AutomationAutomates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.Coding · MIT Finishing a development branchUse when implementation is complete, all tests pass, and you need to decide how to integrate the workCoding · MIT Using git worktreesUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackCoding · MIT Claude Code Skill (Slash Command): review-and-commit.mdA slash command for Claude Code to perform (a) commit(s) following the conventional style.Coding · CC0-1.0

Browse more free Claude skills or everything in Development.