ci-pipeline

Generates CI/CD pipeline configurations for GitHub Actions, GitLab CI, and CircleCI.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/medispis/opencode-config --skill ci-pipeline-medispis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ci-pipeline
Source: https://github.com/medispis/opencode-config/tree/main/skills/ci-pipeline
Command: npx skills add https://github.com/medispis/opencode-config --skill ci-pipeline-medispis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up CI/CD pipelines from scratch requires knowing each platform's YAML syntax, caching strategies, and deployment patterns, which is repetitive and error-prone across projects. ## Core Features & Use Cases - Automatic Stack Detection: Detects the project's language, framework, package manager, and existing CI config before generating anything. - Multi-Platform Generation: Produces pipeline configs for GitHub Actions, GitLab CI, CircleCI, Jenkins, and Bitbucket Pipelines with lint, test, build, and deploy stages. - Best Practices Built In: Enforces dependency caching, matrix builds, pinned action versions, secret usage, and separated CI/CD workflows. - Use Case: You have a Node.js project with no CI. The skill detects npm scripts, then generates a GitHub Actions workflow with lint and test jobs across Node 18, 20, and 22, plus a deploy job gated behind environment protection rules. ## Quick Start Generate a GitHub Actions CI pipeline for this project with lint, test, and build stages using the existing npm scripts.

Frequently Asked Questions about ci-pipeline

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?

The skill detects your language, package manager, and test/build commands from package.json or Makefile, then generates a workflow with lint, test, and build jobs. It includes dependency caching and matrix builds across runtime versions.

Which CI platforms are supported for pipeline generation?

Supported platforms are GitHub Actions, GitLab CI, CircleCI, Jenkins, and Bitbucket Pipelines. The skill detects existing config files like .gitlab-ci.yml or Jenkinsfile, and defaults to GitHub Actions when none exist.

Will it overwrite my existing CI configuration?

No. The skill checks for existing CI files first and asks before overwriting. If a config already exists, it follows the project's established conventions instead of generating from scratch.

Does the pipeline support Docker builds?

Yes. If a Dockerfile exists in the project, the generated pipeline includes docker build and push jobs. Registry credentials are referenced through secrets rather than hardcoded values.

What CI/CD best practices does the generated pipeline enforce?

Generated pipelines cache dependencies, use matrix builds for compatibility testing, separate CI from CD workflows, pin action versions like actions/checkout@v4, use secrets for credentials, and set job timeouts.