ci-cd-pipeline-builder
$
npx mdskill add alirezarezvani/claude-skills/ci-cd-pipeline-builder**Tier:** POWERFUL **Category:** Engineering **Domain:** DevOps / Automation
SKILL.md
.github/skills/ci-cd-pipeline-builderView on GitHub ↗
--- name: "ci-cd-pipeline-builder" description: "Generate pragmatic CI/CD pipelines from detected project stack signals — fast baseline generation, repeatable checks, environment-aware deployment stages. Use when setting up CI for a new project, refactoring existing pipelines, or standardizing deployment workflows across multiple repos." --- # CI/CD Pipeline Builder **Tier:** POWERFUL **Category:** Engineering **Domain:** DevOps / Automation ## Overview 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. ## Core Capabilities - 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 ## When to Use - 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 ## Key Workflows ### 1. Detect Stack ```bash python3 scripts/stack_detector.py --repo . --format text python3 scripts/stack_detector.py --repo . --format json > detected-stack.json ``` Supports input via stdin or `--input` file for offline analysis payloads. ### 2. Generate Pipeline From Detection ```bash python3 scripts/pipeline_generator.py \ --input detected-stack.json \ --platform github \ --output .github/workflows/ci.yml \ --format text ``` Or end-to-end from repo directly: ```bash python3 scripts/pipeline_generator.py --repo . --platform gitlab --output .gitlab-ci.yml ``` ### 3. Validate Before Merge 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. ### 4. Add Deployment Stages Safely - Start with CI-only (`lint/test/build`). - Add staging deploy with explicit environment context. - Add production deploy with manual gate/approval. - Keep rollout/rollback commands explicit and auditable. ## Script Interfaces - `python3 scripts/stack_detector.py --help` - Detects stack signals from repository files - Reads optional JSON input from stdin/`--input` - `python3 scripts/pipeline_generator.py --help` - Generates GitHub/GitLab YAML from detection payload - Writes to stdout or `--output` ## References - [references/pipeline-design-notes.md](references/pipeline-design-notes.md) — common pitfalls, best practices, detection heuristics, generation strategy, platform decision notes, pre-merge validation checklist, and scaling guidance - [references/github-actions-templates.md](references/github-actions-templates.md) - [references/gitlab-ci-templates.md](references/gitlab-ci-templates.md) - [references/deployment-gates.md](references/deployment-gates.md) - [README.md](README.md)
More from alirezarezvani/claude-skills
- a11y-auditAccessibility audit skill for scanning, fixing, and verifying WCAG 2.2 Level A and AA compliance across React, Next.js, Vue, Angular, Svelte, and plain HTML codebases. Use when auditing accessibility, fixing a11y violations, checking color contrast, generating compliance reports, or integrating accessibility checks into CI/CD pipelines.
- ab-test-setupWhen the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "conversion experiment," "statistical significance," or "test this." For tracking implementation, see analytics-tracking.
- ad-creativeWhen the user needs to generate, iterate, or scale ad creative for paid advertising. Use when they say 'write ad copy,' 'generate headlines,' 'create ad variations,' 'bulk creative,' 'iterate on ads,' 'ad copy validation,' 'RSA headlines,' 'Meta ad copy,' 'LinkedIn ad,' or 'creative testing.' This is pure creative production — distinct from paid-ads (campaign strategy). Use ad-creative when you need the copy, not the campaign plan.
- adversarial-reviewerAdversarial code review that breaks the self-review monoculture. Use when you want a genuinely critical review of recent changes, before merging a PR, or when you suspect Claude is being too agreeable about code quality. Forces perspective shifts through hostile reviewer personas that catch blind spots the author's mental model shares with the reviewer.
- aeoAnswer Engine Optimization (AEO) skill — optimize content to be cited by AI language models (ChatGPT, Perplexity, Claude, Gemini, Mistral) as authoritative sources. Distinct from SEO — AEO optimizes for citation in LLM-generated responses, not search rankings. Use when planning content for AI-first search audiences, auditing existing content for E-E-A-T signals, tracking which pages get cited by which LLMs, or building a citation-friendly content strategy. Triggers — 'AEO audit', 'optimize for ChatGPT', 'get cited by Perplexity', 'LLM citation strategy', 'answer engine optimization', 'content for AI search', 'E-E-A-T audit'. Output is a markdown audit report (default) or JSON for pipeline integration. Stdlib-only Python tools.
- agent-designerUse when the user asks to design a multi-agent system, pick an orchestration pattern (supervisor/swarm/pipeline), generate tool schemas for agents, or evaluate agent execution logs for cost, latency, and failure bottlenecks. Examples: 'design an agent architecture for research automation', 'generate Anthropic tool schemas from these tool descriptions', 'analyze these agent run logs for bottlenecks'. NOT for Claude Code workflow files (use workflow-builder) or single-agent prompt design (use agent-workflow-designer).
- agent-protocolInter-agent communication protocol for C-suite agent teams. Defines invocation syntax, loop prevention, isolation rules, and response formats. Use when C-suite agents need to query each other, coordinate cross-functional analysis, or run board meetings with multiple agent roles.
- agent-workflow-designerDesign production-grade multi-agent workflows with clear pattern choice (sequential, parallel, hierarchical), handoff contracts, failure handling, and cost/context controls. Use when architecting a multi-step agent pipeline, choosing between single-agent vs multi-agent approaches, or refactoring an LLM workflow that suffers from context bloat or unreliable handoffs.
- agenthubMulti-agent collaboration plugin that spawns N parallel subagents competing on the same task via git worktree isolation. Agents work independently, results are evaluated by metric or LLM judge, and the best branch is merged. Use when: user wants multiple approaches tried in parallel — code optimization, content variation, research exploration, or any task that benefits from parallel competition. Requires: a git repo.
- agile-product-ownerAgile product ownership for backlog management and sprint execution. Covers user story writing, acceptance criteria, sprint planning, and velocity tracking. Use when writing user stories, creating acceptance criteria, planning sprints, estimating story points, breaking down epics, or prioritizing the backlog.