ci-pipeline-setup

Generates platform-specific CI/CD pipeline configs and pipeline specification documents for new branches.

Updated May 21, 2026
One-click install
npx skills add https://github.com/CagesThrottleUs/private-ai-harness --skill ci-pipeline-setup-cagesthrottleus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ci-pipeline-setup
Source: https://github.com/CagesThrottleUs/private-ai-harness/tree/main/skills/ci-pipeline-setup
Command: npx skills add https://github.com/CagesThrottleUs/private-ai-harness --skill ci-pipeline-setup-cagesthrottleus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? New branches and projects often ship code before any CI exists, leaving merges ungated until a pipeline is retrofitted at PR time. This Skill detects the CI platform and project stack, then produces a pipeline specification and working configuration before any feature code is written. ## Core Features & Use Cases - Platform Detection and Config Generation: Detects GitHub Actions, GitLab CI, Jenkins, CircleCI, Azure DevOps, or Bitbucket Pipelines from existing config files and generates the matching pipeline YAML with lint, type check, test, security scan, build, and deploy stages. - Pipeline Spec Document: Writes a technology-agnostic specification covering stage ordering, coverage gates (80% line), mutation testing thresholds, SLSA/SBOM supply-chain integrity, secrets management, and branch protection rules. - Reviewer Validation Loop: Dispatches a ci-reviewer agent on the generated artifacts and iterates fixes until all Critical findings are resolved before committing. - Use Case: After creating a worktree for a new feature in a Python project with no CI, run this Skill to produce a GitHub Actions workflow with coverage gates, Dependabot config, and branch protection guidance committed on the first push. ## Quick Start Set up a CI pipeline for this repository before I start writing feature code, detecting the platform and generating the config plus spec document.

Frequently Asked Questions about ci-pipeline-setup

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

FAQPage Schema
How do I set up a CI pipeline for a new project?

Detect the platform from existing config files (.github/workflows, .gitlab-ci.yml, Jenkinsfile), then generate a pipeline spec and platform config with lint, type check, unit tests with an 80% coverage gate, security scan, build, and staged deploys. Commit the config so CI guards from the first push.

What stages should a CI/CD pipeline include?

Order stages fail-fast: lint and format, type check, unit tests with coverage gate, mutation testing, integration tests, SAST/SCA security scans, then build the artifact once and deploy to staging with health checks and smoke tests before a gated production deploy.

Does this work with GitLab CI or only GitHub Actions?

It supports GitHub Actions, GitLab CI, Jenkins, CircleCI, Azure DevOps, and Bitbucket Pipelines. The platform is auto-detected from existing config files, and the same universal stage structure is adapted to each platform's YAML syntax.

How do I enforce a code coverage threshold in CI?

Add a coverage gate to the unit test stage that fails the pipeline below 80% line coverage and 70% branch coverage, using tools like pytest-cov, jest --coverage, go test -cover, cargo tarpaulin, or jacoco depending on the language.

When should I skip generating a new CI pipeline?

Skip when a comprehensive pipeline already exists and passes the ci-reviewer agent with no Critical findings. In that case, run the reviewer on the existing config instead of regenerating stages that are already correct.