Verified:GitHub

ci-cd-pipeline-builder

Detects repository stack signals and generates GitHub Actions or GitLab CI pipeline YAML.

Updated May 21, 2025

Search Tags:#devops #github actions #yaml #ci-cd #gitlab ci #pipeline generation #stack detection

One-click install

npx skills add https://github.com/nielslataire/Group-LN --skill ci-cd-pipeline-builder-nielslataire

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: ci-cd-pipeline-builder
Source: https://github.com/nielslataire/Group-LN/tree/main/.claude/skills/ci-cd-pipeline-builder
Command: npx skills add https://github.com/nielslataire/Group-LN --skill ci-cd-pipeline-builder-nielslataire

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Setting up CI pipelines from scratch often means copying brittle templates that don't match the actual project stack, leading to broken builds, missing cache keys, and mismatched lint/test/build commands. ## Core Features & Use Cases - Stack Detection: Scans repository files (package.json, lockfiles, pyproject.toml, go.mod, Dockerfile) to identify languages, package managers, and available lint/test/build commands, outputting text or JSON reports. - Pipeline Generation: Produces GitHub Actions or GitLab CI YAML from the detection payload, with appropriate runtime setup, dependency installation, and staged lint/test/build jobs. - Deployment Guidance: Includes references for deployment gates, environment promotion patterns, and rollback requirements. - Use Case: Bootstrap CI for a new Node.js repository by running the stack detector, then generating a .github/workflows/ci.yml that uses npm ci with caching and runs the project's actual lint, test, and build scripts. ## Quick Start Ask the AI to detect the stack of the current repository and generate a GitHub Actions CI workflow file from the detected signals.

Frequently Asked Questions about ci-cd-pipeline-builder

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I generate a GitHub Actions workflow from my repository?▼

Run scripts/stack_detector.py with --repo to produce a JSON stack report, then pass it to scripts/pipeline_generator.py with --platform github and --output .github/workflows/ci.yml. You can also skip detection and use --repo directly on the generator.

How do I create a GitLab CI pipeline for a Node.js project?▼

Run scripts/pipeline_generator.py with --repo pointing at your project and --platform gitlab. It detects package.json and lockfiles, selects npm, yarn, or pnpm install commands, and writes lint, test, and build stages to .gitlab-ci.yml.

What languages does the stack detector support?▼

The detector identifies Node.js via package.json, Python via pyproject.toml or requirements.txt, and Go via go.mod. It also detects signals like Dockerfiles, Helm charts, and Kubernetes directories, though pipeline generation covers Node, Python, and Go.

Does the pipeline generator require any Python packages?▼

No external dependencies are required. Both scripts use only the Python 3 standard library (argparse, json, pathlib, dataclasses), so they run on any system with Python 3 installed.

What happens when my project has no lint or test scripts?▼

The generator inserts conservative placeholder commands like echo statements when lint, test, or build scripts are missing from package.json. You should replace these placeholders with real commands before merging the pipeline.

When should I not use generated CI pipelines?▼

Generated pipelines are baselines, not production-hardened configurations. Avoid enabling deploy jobs before tests are stable, and add branch protections, secret management, and manual approval gates for production deployments separately.