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.
Overview
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.
Source: https://github.com/alirezarezvani/claude-skills · MIT · © 2025 Alireza Rezvani
System prompt
The instruction block that defines the agent's role, rules and output format.
# 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) User prompt template
Fill in the variables and send it to run the skill: {{variables}}
Variables
| Name | Required | Description | Example |
|---|
Full skill configuration
The standard .aiskill file in JSON and YAML.
{
"format": "aiskill/v1",
"skill": {
"name": "ci-cd-pipeline-builder",
"slug": "ci-cd-pipeline-builder",
"version": "1.0.0",
"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.",
"category": "Development",
"tags": [
"engineering"
],
"platforms": [
"chatgpt",
"claude-code",
"cursor"
],
"tested_environment": "Agent Skills convention (SKILL.md) — works with Claude Code, Cursor, ChatGPT/Codex and compatible agents",
"license": "MIT"
},
"prompts": {
"system": "# CI/CD Pipeline Builder\r\n\r\n**Tier:** POWERFUL \r\n**Category:** Engineering \r\n**Domain:** DevOps / Automation\r\n\r\n## Overview\r\n\r\nUse 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.\r\n\r\n## Core Capabilities\r\n\r\n- Detect language/runtime/tooling from repository files\r\n- Recommend CI stages (`lint`, `test`, `build`, `deploy`)\r\n- Generate GitHub Actions or GitLab CI starter pipelines\r\n- Include caching and matrix strategy based on detected stack\r\n- Emit machine-readable detection output for automation\r\n- Keep pipeline logic aligned with project lockfiles and build commands\r\n\r\n## When to Use\r\n\r\n- Bootstrapping CI for a new repository\r\n- Replacing brittle copied pipeline files\r\n- Migrating between GitHub Actions and GitLab CI\r\n- Auditing whether pipeline steps match actual stack\r\n- Creating a reproducible baseline before custom hardening\r\n\r\n## Key Workflows\r\n\r\n### 1. Detect Stack\r\n\r\n```bash\r\npython3 scripts/stack_detector.py --repo . --format text\r\npython3 scripts/stack_detector.py --repo . --format json > detected-stack.json\r\n```\r\n\r\nSupports input via stdin or `--input` file for offline analysis payloads.\r\n\r\n### 2. Generate Pipeline From Detection\r\n\r\n```bash\r\npython3 scripts/pipeline_generator.py \\\r\n --input detected-stack.json \\\r\n --platform github \\\r\n --output .github/workflows/ci.yml \\\r\n --format text\r\n```\r\n\r\nOr end-to-end from repo directly:\r\n\r\n```bash\r\npython3 scripts/pipeline_generator.py --repo . --platform gitlab --output .gitlab-ci.yml\r\n```\r\n\r\n### 3. Validate Before Merge\r\n\r\n1. Confirm commands exist in project (`test`, `lint`, `build`).\r\n2. Run generated pipeline locally where possible.\r\n3. Ensure required secrets/env vars are documented.\r\n4. Keep deploy jobs gated by protected branches/environments.\r\n\r\n### 4. Add Deployment Stages Safely\r\n\r\n- Start with CI-only (`lint/test/build`).\r\n- Add staging deploy with explicit environment context.\r\n- Add production deploy with manual gate/approval.\r\n- Keep rollout/rollback commands explicit and auditable.\r\n\r\n## Script Interfaces\r\n\r\n- `python3 scripts/stack_detector.py --help`\r\n - Detects stack signals from repository files\r\n - Reads optional JSON input from stdin/`--input`\r\n- `python3 scripts/pipeline_generator.py --help`\r\n - Generates GitHub/GitLab YAML from detection payload\r\n - Writes to stdout or `--output`\r\n\r\n## References\r\n\r\n- [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\r\n- [references/github-actions-templates.md](references/github-actions-templates.md)\r\n- [references/gitlab-ci-templates.md](references/gitlab-ci-templates.md)\r\n- [references/deployment-gates.md](references/deployment-gates.md)\r\n- [README.md](README.md)",
"user_template": ""
},
"variables": [],
"install": {
"steps": [
{
"title": "Download & unzip",
"detail": "Download the .zip package from SkillVault and unzip it. The ci-cd-pipeline-builder/ folder contains SKILL.md plus any companion scripts, references and assets."
},
{
"title": "Copy into your agent skills directory",
"detail": "Move the folder into your agent's skills directory — e.g. ~/.claude/skills/ (Claude Code), .codex/skills/, .cursor/skills/ or your project's .claude/skills/ folder — then restart or reload the session."
},
{
"title": "Use it",
"detail": "Describe the task in natural language; the agent loads the skill automatically when the request matches the skill description."
}
]
},
"usage": {
"steps": []
},
"metadata": {
"author": "SkillVault",
"source": "https://skillvault.top/skills/ci-cd-pipeline-builder",
"exported_at": "2026-11-03T07:43:38.870Z"
}
} format: aiskill/v1
skill:
name: ci-cd-pipeline-builder
slug: ci-cd-pipeline-builder
version: 1.0.0
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.
category: Development
tags:
- engineering
platforms:
- chatgpt
- claude-code
- cursor
tested_environment: >-
Agent Skills convention (SKILL.md) — works with Claude Code, Cursor, ChatGPT/Codex and
compatible agents
license: MIT
prompts:
system: "# CI/CD Pipeline Builder\r\n\r\n**Tier:** POWERFUL \r\n**Category:** Engineering \r\n**Domain:** DevOps / Automation\r\n\r\n## Overview\r\n\r\nUse 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.\r\n\r\n## Core Capabilities\r\n\r\n- Detect language/runtime/tooling from repository files\r\n- Recommend CI stages (`lint`, `test`, `build`, `deploy`)\r\n- Generate GitHub Actions or GitLab CI starter pipelines\r\n- Include caching and matrix strategy based on detected stack\r\n- Emit machine-readable detection output for automation\r\n- Keep pipeline logic aligned with project lockfiles and build commands\r\n\r\n## When to Use\r\n\r\n- Bootstrapping CI for a new repository\r\n- Replacing brittle copied pipeline files\r\n- Migrating between GitHub Actions and GitLab CI\r\n- Auditing whether pipeline steps match actual stack\r\n- Creating a reproducible baseline before custom hardening\r\n\r\n## Key Workflows\r\n\r\n### 1. Detect Stack\r\n\r\n```bash\r\npython3 scripts/stack_detector.py --repo . --format text\r\npython3 scripts/stack_detector.py --repo . --format json > detected-stack.json\r\n```\r\n\r\nSupports input via stdin or `--input` file for offline analysis payloads.\r\n\r\n### 2. Generate Pipeline From Detection\r\n\r\n```bash\r\npython3 scripts/pipeline_generator.py \\\r\n --input detected-stack.json \\\r\n --platform github \\\r\n --output .github/workflows/ci.yml \\\r\n --format text\r\n```\r\n\r\nOr end-to-end from repo directly:\r\n\r\n```bash\r\npython3 scripts/pipeline_generator.py --repo . --platform gitlab --output .gitlab-ci.yml\r\n```\r\n\r\n### 3. Validate Before Merge\r\n\r\n1. Confirm commands exist in project (`test`, `lint`, `build`).\r\n2. Run generated pipeline locally where possible.\r\n3. Ensure required secrets/env vars are documented.\r\n4. Keep deploy jobs gated by protected branches/environments.\r\n\r\n### 4. Add Deployment Stages Safely\r\n\r\n- Start with CI-only (`lint/test/build`).\r\n- Add staging deploy with explicit environment context.\r\n- Add production deploy with manual gate/approval.\r\n- Keep rollout/rollback commands explicit and auditable.\r\n\r\n## Script Interfaces\r\n\r\n- `python3 scripts/stack_detector.py --help`\r\n - Detects stack signals from repository files\r\n - Reads optional JSON input from stdin/`--input`\r\n- `python3 scripts/pipeline_generator.py --help`\r\n - Generates GitHub/GitLab YAML from detection payload\r\n - Writes to stdout or `--output`\r\n\r\n## References\r\n\r\n- [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\r\n- [references/github-actions-templates.md](references/github-actions-templates.md)\r\n- [references/gitlab-ci-templates.md](references/gitlab-ci-templates.md)\r\n- [references/deployment-gates.md](references/deployment-gates.md)\r\n- [README.md](README.md)"
user_template: ""
variables: []
install:
steps:
- title: Download & unzip
detail: >-
Download the .zip package from SkillVault and unzip it. The ci-cd-pipeline-builder/ folder
contains SKILL.md plus any companion scripts, references and assets.
- title: Copy into your agent skills directory
detail: >-
Move the folder into your agent's skills directory — e.g. ~/.claude/skills/ (Claude Code),
.codex/skills/, .cursor/skills/ or your project's .claude/skills/ folder — then restart or
reload the session.
- title: Use it
detail: >-
Describe the task in natural language; the agent loads the skill automatically when the
request matches the skill description.
usage:
steps: []
metadata:
author: SkillVault
source: https://skillvault.top/skills/ci-cd-pipeline-builder
exported_at: "2026-11-03T07:43:38.870Z"
Installation guide
- 1
Download & unzip
Download the .zip package from SkillVault and unzip it. The ci-cd-pipeline-builder/ folder contains SKILL.md plus any companion scripts, references and assets.
- 2
Copy into your agent skills directory
Move the folder into your agent's skills directory — e.g. ~/.claude/skills/ (Claude Code), .codex/skills/, .cursor/skills/ or your project's .claude/skills/ folder — then restart or reload the session.
- 3
Use it
Describe the task in natural language; the agent loads the skill automatically when the request matches the skill description.
How to use
Platform compatibility
ChatGPT GPTs
OpenAI
Paste the system prompt into the GPT "Instructions" field and keep the user template as your starter message.
Official docsClaude Code
Anthropic
Save the exported .aiskill JSON as a skill file in your project or paste the system prompt into CLAUDE.md / a slash-command markdown file.
Official docsCursor
Anysphere
Copy the system prompt into .cursor/rules/*.mdc (or Project Rules in Settings) and reference the user template in your agent prompts.
Official docsRelated skills
aws-solution-architect
Design AWS architectures for startups using serverless patterns and IaC templates. Use when asked to design serverless architecture, create CloudFormation templates, optimize AWS costs, set up CI/CD pipelines, or migrate to AWS. Covers Lambda, API Gateway, DynamoDB, ECS, Aurora, and cost optimization.
azure-cloud-architect
Design Azure architectures for startups and enterprises. Use when asked to design Azure infrastructure, create Bicep/ARM templates, optimize Azure costs, set up Azure DevOps pipelines, or migrate to Azure. Covers AKS, App Service, Azure Functions, Cosmos DB, and cost optimization.
browser-automation
Use when the user asks to automate browser tasks, scrape websites, fill forms, capture screenshots, extract structured data from web pages, or build web automation workflows. NOT for testing — use playwright-pro for that.