ci-cd-pipeline-builder

Topics in the source

• CI/CD Pipeline Builder
• Overview
• Core Capabilities
• When to Use
• Key Workflows
• 1. Detect Stack
• 2. Generate Pipeline From Detection
• 3. Validate Before Merge

Tier: POWERFUL Category: Engineering Domain: DevOps / Automation Use this skill to generate pragmatic CI/CD pipelines from detected project stack signals, not guesswork. It focuses on fast baseline generation, repeatable checks, and environment-aware deployment stages. Detect language/runtime/tooling from repository files Recommend CI stages (lint, test, build, deploy) Generate GitHub Actions or GitLab CI starter pipelines Include caching and matrix strategy based on detected stack Emit machine-readable detection output for automation Keep pipeline logic aligned with project lockfiles and build commands Bootstrapping CI for a new repository Replacing brittle copied pipeline files Migrating between GitHub Actions and GitLab CI Auditing whether pipeline steps match actual stack Creating a reproducible baseline before custom hardening Supports input via stdin or --input file for offline analysis payloads. Or end-to-end from repo directly: 1. Confirm commands exist in project (test, lint, build). 2. Run generated pipeline locally where possible. 3. Ensure required secrets/env vars are documented. 4. Keep deploy jobs gated by protected branches/environments. Start with CI-only (lint/tes

This is an excerpt. Refer to the complete source and its current requirements.