How do I install the CI CD Pipeline Builder skill?

Run npx skillmds@latest add mhassan0000/ci-cd-pipeline-builder in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is CI CD Pipeline Builder safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with CI CD Pipeline Builder?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is CI CD Pipeline Builder free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published CI CD Pipeline Builder?

MHassan0000 (@mhassan0000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

CI CD Pipeline Builder by mhassan0000

Name: CI CD Pipeline Builder
Author: MHassan0000

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.

MHassan0000 Updated Sep 17, 2026 1 repo stars

File contents

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

---name: ci-cd-pipeline-builderdescription: 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## OverviewUse 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```bashpython3 scripts/stack_detector.py --repo . --format textpython3 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```bashpython3 scripts/pipeline_generator.py \ --input detected-stack.json \ --platform github \ --output .github/workflows/ci.yml \ --format text```Or end-to-end from repo directly:```bashpython3 scripts/pipeline_generator.py --repo . --platform gitlab --output .gitlab-ci.yml```### 3. Validate Before Merge1. 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)

Frequently asked questions