Verified:GitHub

building-cicd-pipelines

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

1|Updated Feb 10, 2026

Search Tags:#ci/cd #github actions #deployment automation #pipeline #jenkins #gitlab ci #gitea actions

One-click install

npx skills add https://github.com/stefanfaur/roach-marketplace --skill building-cicd-pipelines-stefanfaur

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: building-cicd-pipelines
Source: https://github.com/stefanfaur/roach-marketplace/tree/main/ci-cd-pipeline-builder/skills/building-cicd-pipelines
Command: npx skills add https://github.com/stefanfaur/roach-marketplace --skill building-cicd-pipelines-stefanfaur

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Writing CI/CD pipeline configuration by hand is error-prone and platform-specific, especially when targeting multiple platforms like GitHub Actions and Gitea Actions that have subtle compatibility differences. This Skill guides the design, implementation, and validation of pipeline workflows across four major CI/CD platforms. ## Core Features & Use Cases - Multi-Platform Pipeline Generation: Creates workflow files for GitHub Actions (`.github/workflows/`), Gitea Actions (`.gitea/workflows/`), GitLab CI (`.gitlab-ci.yml`), and Jenkins (`Jenkinsfile`). - Gitea Actions Compatibility Rules: Applies a detailed checklist covering ignored syntax (`concurrency`, `permissions`, `timeout-minutes`), unsupported status functions, PAT-based registry auth, and CodeQL replacement with Trivy or Semgrep. - Structured Five-Step Workflow: Walks through platform selection, pipeline architecture design, implementation, validation, and deployment monitoring. - Use Case: A team migrating from GitHub to a self-hosted Gitea instance needs their workflows ported. The Skill rewrites the pipelines, removes unsupported syntax, swaps token authentication for PATs, and replaces CodeQL with Trivy scanning. ## Quick Start Ask the assistant to create a CI/CD pipeline for your project on GitHub Actions or Gitea Actions, including test, build, security scan, and deployment stages.

Frequently Asked Questions about building-cicd-pipelines

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

FAQPage Schema

How do I create a CI/CD pipeline for GitHub Actions?▼

Define workflow YAML files in `.github/workflows/` with stages for test, build, security, and deploy. Configure triggers like push or pull request, set up secrets, pin actions to specific versions, and test in a non-production branch before merging.

How do I make GitHub Actions workflows compatible with Gitea Actions?▼

Place workflows in `.gitea/workflows/` and remove `concurrency`, `permissions`, `timeout-minutes`, `continue-on-error`, and `environment` blocks, which Gitea silently ignores. Use only `always()` for status checks, keep `runs-on` values simple, and replace `GITHUB_TOKEN` package publishing with Personal Access Tokens.

Does Gitea Actions support CodeQL code scanning?▼

No, `github/codeql-action` is not available on Gitea Actions. Use alternative SAST tools such as Trivy or Semgrep in your security scanning stage instead.

Why does my Gitea Actions workflow fail to push to the package registry?▼

The built-in `GITEA_TOKEN` cannot authenticate pushes to Gitea package registries. Create a Personal Access Token, store it as a repository secret, and use it for registry authentication in the workflow.

Which CI/CD platforms does this pipeline builder support?▼

It supports GitHub Actions, Gitea Actions, GitLab CI, and Jenkins. Each platform uses its native configuration format: workflow YAML for GitHub and Gitea, `.gitlab-ci.yml` for GitLab, and `Jenkinsfile` for Jenkins.