mcpField
C
ci-cd-pipeline-builder

ci-cd-pipeline-builder

github.com/alirezarezvaniCloud & DevOps28.9k689 installsUpdated 2d ago
Repository

About ci-cd-pipeline-builder

A skill for engineering teams that detects a repository’s stack from its files and generates a CI/CD pipeline suited to the project. It supports GitHub Actions and GitLab CI and can emit detection results for automation.

Key features

  1. 01Detect languages and tooling from repository files
  2. 02Recommend lint, test, build, and deploy stages
  3. 03Generate GitHub Actions or GitLab CI configuration
  4. 04Support caching and matrix strategies
  5. 05Emit machine-readable detection results

Use cases

  1. 01Bootstrap CI for a new repository
  2. 02Migrate between GitHub Actions and GitLab CI
  3. 03Check whether pipeline steps match the project stack
  4. 04Create a reproducible baseline before deployment

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/alirezarezvani/claude-skills --skill ci-cd-pipeline-builder

After installing, type/ci-cd-pipeline-builderin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

README.md
references/
deployment-gates.md
github-actions-templates.md
gitlab-ci-templates.md
pipeline-design-notes.md
scripts/
pipeline_generator.py
stack_detector.py

Details

From the project README

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
  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

Comments

Markdown supported