Verified:GitHub

ci-cd-pipeline-builder

Detect repository stack signals and generate GitHub Actions or GitLab CI pipeline YAML.

2|Updated Mar 24, 2026

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

One-click install

npx skills add https://github.com/BryanPinheiro77/FinanceBot-BackEnd --skill ci-cd-pipeline-builder-bryanpinheiro77

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: ci-cd-pipeline-builder
Source: https://github.com/BryanPinheiro77/FinanceBot-BackEnd/tree/main/.agents/skills/ci-cd-pipeline-builder
Command: npx skills add https://github.com/BryanPinheiro77/FinanceBot-BackEnd --skill ci-cd-pipeline-builder-bryanpinheiro77

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 YAML from other projects that doesn't match the actual stack. This Skill detects languages, package managers, and build commands from repository files, then generates a matching GitHub Actions or GitLab CI baseline with lint, test, and build stages. ## Core Features & Use Cases - Stack Detection: Scans lockfiles, manifests, and scripts to identify Node, Python, Go, Terraform, and Docker stacks, emitting JSON or text reports. - Pipeline Generation: Produces GitHub Actions or GitLab CI YAML with caching, stage separation, and detected lint/test/build commands. - Deployment Guidance: Reference notes cover deployment gates, protected environments, rollback requirements, and pre-merge validation checklists. - Use Case: When bootstrapping CI for a new repository, run the stack detector, feed the JSON report into the generator, and commit a working pipeline aligned with the project's actual tooling. ## Quick Start Ask the assistant to detect the stack of the current repository and generate a GitHub Actions CI workflow file from the detection results.

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 stack_detector.py with --repo pointing at your project to produce a JSON stack report, then pass it to pipeline_generator.py with --platform github and --output .github/workflows/ci.yml. The generator writes a workflow with lint, test, and build steps matching your detected stack.

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

Run pipeline_generator.py with --platform gitlab and either --repo for auto-detection or --input with a stack report JSON. It emits a .gitlab-ci.yml with lint, test, and build stages using the node:20 image and the install command matching your lockfile.

Which languages and tools does the stack detector support?▼

The detector recognizes Node.js via package.json and lockfiles, Python via pyproject.toml or requirements.txt, Go via go.mod, Terraform via .tf files, and Docker via Dockerfile. It also detects pnpm, yarn, and npm to select the correct install command.

Does the pipeline generator require external Python packages?▼

No, both scripts use only the Python 3 standard library (argparse, json, pathlib, dataclasses). You can run them directly with python3 without installing any dependencies.

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

The generator falls back to conservative placeholder commands like echo statements so the pipeline still parses and runs. You should replace these placeholders with real commands before merging.

When should I not rely on the generated pipeline as-is?▼

The generated baseline is CI-only and intentionally minimal. Before production use, add deployment stages with protected environments, document required secrets, and validate that all referenced commands exist in the repository.