Verified:GitHub

ci-cd-pipeline-builder

Generate GitHub Actions or GitLab CI pipelines from detected repository stack signals.

Updated Aug 14, 2026

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

One-click install

npx skills add https://github.com/Rohithdgrr/REEK-uninstaller --skill ci-cd-pipeline-builder-rohithdgrr

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: ci-cd-pipeline-builder
Source: https://github.com/Rohithdgrr/REEK-uninstaller/tree/main/.opencode/skills/ci-cd-pipeline-builder
Command: npx skills add https://github.com/Rohithdgrr/REEK-uninstaller --skill ci-cd-pipeline-builder-rohithdgrr

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Setting up CI/CD pipelines from scratch often means copying brittle YAML from other projects that does not match the actual stack, leading to broken builds, missing cache keys, and ungated deploy jobs. This Skill detects the real languages, package managers, and scripts in a repository and generates a matching pipeline baseline. ## Core Features & Use Cases - Stack Detection: Scans repository files (package.json, lockfiles, pyproject.toml, go.mod, Dockerfile, Terraform) to identify languages, package managers, and available lint/test/build commands, outputting text or machine-readable JSON. - Pipeline Generation: Produces GitHub Actions or GitLab CI YAML with lint, test, and build stages, correct install commands per lockfile (npm ci, pnpm, yarn), and caching configuration. - Deployment Guidance: Reference notes cover deployment gates, branch protection, rollback requirements, and platform decision criteria. - Use Case: When bootstrapping CI for a new Node.js repository, run the stack detector to produce a JSON report, then feed it to the generator to write a ready-to-commit .github/workflows/ci.yml with npm caching and your actual lint/test/build scripts. ## Quick Start Ask the AI to detect the stack in 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 for my project?▼

Run the stack detector script against your repository to produce a JSON report, then pass it to the pipeline generator with --platform github and an --output path. It writes a workflow with checkout, runtime setup, dependency install, and your detected lint, test, and build commands.

How to create a GitLab CI pipeline from an existing repository?▼

Run the pipeline generator with --repo pointing at your project and --platform gitlab. It auto-detects Node, Python, Go, Terraform, or Docker signals and writes a .gitlab-ci.yml with lint, test, and build stages using the appropriate container images.

GitHub Actions vs GitLab CI for a new project pipeline?▼

GitHub Actions fits teams already on GitHub needing tight ecosystem integration, while GitLab CI suits self-hosted environments combining SCM and CI. The generator supports both platforms from the same detection payload, so you can compare outputs before committing.

Does the pipeline generator support pnpm or yarn projects?▼

Yes, the stack detector checks for pnpm-lock.yaml and yarn.lock and selects the matching frozen-lockfile install command. If neither lockfile exists, it falls back to npm ci for Node.js projects.

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

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

Why does my generated pipeline fail on the first run?▼

Common causes are referenced commands that do not exist in the repo, missing secrets, or a cache strategy mismatched to your package manager. Validate the YAML parses, confirm every command exists, and document required secrets before merging.