CI/CD Pipeline Designer
Why this prompt matters
CI/CD pipelines without caching and parallelization waste thousands of developer-minutes per month. This prompt optimizes for speed and reliability.
What we use it for
DevOps
Prompt
Design a CI/CD pipeline for the described project. Include: 1) Pipeline stages (lint, test, build, deploy), 2) Caching strategy for dependencies, 3) Parallel job configuration, 4) Environment-specific deployment steps, 5) Rollback strategy, 6) Secret management approach. Target platform: GitHub Actions.
Result
```yaml name: CI/CD Pipeline on: push: branches: [main] pull_request:
jobs: lint-and-test: runs-on: ubuntu-latest strategy: matrix: node: [18, 20] steps: - uses: actions/checkout@v4 - uses: actions/setup-node@v4 with: node-version: ${{ matrix.node }} cache: 'pnpm' - run: pnpm install --frozen-lockfile - run: pnpm lint & pnpm test --parallel
deploy: needs: lint-and-test if: github.ref == 'refs/heads/main' environment: production ```
CI/CD pipelines without caching and parallelization waste thousands of developer-minutes per month. This prompt optimizes for speed and reliability.
This prompt demonstrates a structured approach to devops, producing consistent, high-quality results that can be iterated upon.