Back to prompts
Coding & DevelopmentPremiumadvanced
4.8

CI/CD Pipeline Architect

Design a complete CI/CD pipeline — build, test, deploy, monitor — with config files ready to use.

Copy & Paste this prompt
You are a DevOps engineer who has built CI/CD pipelines for teams shipping multiple times per day. Design a complete pipeline for my project.

Project type: [WEB APP / API / MOBILE / LIBRARY / MONOREPO]
Language/Framework: [LANGUAGE + FRAMEWORK]
CI/CD platform: [GitHub Actions / GitLab CI / Jenkins / CircleCI / OTHER]
Deployment target: [AWS / GCP / Azure / Vercel / Netlify / Docker / K8s / OTHER]
Team size: [NUMBER OF DEVELOPERS]
Current process: [MANUAL / BASIC CI / NOTHING]

Build:

1. **PIPELINE ARCHITECTURE**
   - Visual flow: commit → build → test → deploy
   - Branch strategy (main, develop, feature, hotfix)
   - Environment mapping (dev, staging, production)
   - Merge/deploy rules (who can deploy where)

2. **CI CONFIGURATION** (ready to copy)
   - Build step (with caching for speed)
   - Lint + format check
   - Unit tests (with coverage threshold)
   - Integration tests
   - Security scan (dependencies + secrets)
   - Build artifact handling

3. **CD CONFIGURATION**
   - Staging auto-deploy on merge to develop
   - Production deploy on release tag / merge to main
   - Rollback procedure (one-click)
   - Database migration handling
   - Environment variables management

4. **QUALITY GATES**
   - Tests must pass
   - Coverage minimum: [RECOMMEND %]
   - No high/critical security vulnerabilities
   - Build size budget
   - Performance budget (if applicable)

5. **MONITORING & ALERTS**
   - Deploy success/failure notifications (Slack/Discord)
   - Post-deploy health check
   - Error rate monitoring setup
   - Rollback trigger conditions

Output the actual config files (.github/workflows/ci.yml etc.) — not just descriptions.
#ci-cd#devops#github-actions#deployment#automation

Works with

chatgptclaudegemini

💡 Pro Tips

  • •Start with CI only (build + test), add CD once stable
  • •Caching dependencies can cut pipeline time by 50-70%
  • •The rollback procedure is the most important part — test it before you need it

🧠 Why This Works

A well-designed CI/CD pipeline catches bugs before production and deploys with confidence. This prompt produces battle-tested pipeline configurations using caching, parallelization, and proper stage gating—the patterns that mature engineering teams use.

📅 When to Use This Prompt

Use when setting up CI/CD for a new project, when your current pipeline is slow and needs optimization, or when migrating between CI platforms (Jenkins to GitHub Actions, CircleCI to GitLab CI, etc.).

🎯 What You'll Get

You'll receive complete pipeline configuration files with build, test, lint, security scan, and deploy stages—including caching strategies, environment-specific deployments, rollback procedures, and notification setup ready to commit.

🔗 Related Prompts

Coding & DevelopmentPremium

Complete Test Suite Generator

Generate comprehensive unit, integration, and edge case tests for your code — with 90%+ coverage.

testingunit-teststdd
★4.8
intermediate