Coding Prompts
CI/CD Pipeline Generator
Generate a complete GitHub Actions (or other CI) workflow file for any tech stack — with testing, linting, building, and deployment steps.
Prompt
Generate a complete CI/CD pipeline configuration for the following project: PROJECT DETAILS: - Language/Runtime: [e.g., Node.js 22, Python 3.12, Go 1.22, Java 21] - Framework: [e.g., Next.js, Django, Gin, Spring Boot] - Package manager: [npm / yarn / pnpm / pip / poetry / gradle / maven] - Test runner: [e.g., Vitest, Jest, pytest, Go test, JUnit] - Lint tools: [e.g., ESLint, Prettier, Ruff, golangci-lint, Checkstyle] CI PLATFORM: [GitHub Actions / GitLab CI / CircleCI / Bitbucket Pipelines] PIPELINE REQUIREMENTS: - Trigger on: [push to main, PRs, both, scheduled] - Node/Runtime caching: [YES/NO] - Run tests: [YES/NO — include coverage report: YES/NO] - Run linter: [YES/NO] - Build step: [YES/NO — what does build produce?] - Docker build + push: [YES/NO — registry: Docker Hub / ECR / GCR / GHCR] - Deploy to: [Vercel / Railway / AWS ECS / Fly.io / VPS / none] - Environment variables needed: [LIST KEY NAMES — not values] - Branch protection (require CI to pass): [YES/NO] Generate: 1. The complete pipeline YAML file (ready to copy into `.github/workflows/ci.yml` or equivalent) 2. A short explanation of each job and why it's structured that way 3. Any secrets that need to be added to the repo settings (just the names, not values) 4. One optimization tip specific to this stack Use job caching aggressively. Fail fast — put the quickest checks first.
How to use
Paste this prompt when setting up CI for a new project or migrating to a new CI platform. Fill in the details for your exact stack. The output will be a production-ready YAML file that you can drop directly into your repo.
Variables
[Language/Runtime]— be exact with the version; the pipeline will pin it[CI PLATFORM]— GitHub Actions is the most common default; adjust syntax accordingly[Deploy to]— if deploying, specify the platform; the generator will add the right deploy step[LIST KEY NAMES]— list environment variable names likeDATABASE_URL,API_KEY— the generator will tell you which ones to add as repository secrets
Tips
- Always specify a version for your runtime (Node 22, not just Node) — pipelines that use
latestbreak when major versions drop. - "Fail fast" means put lint and type-check before tests — they're faster and cheaper to fail on.
- If you have a monorepo, describe the structure and ask the generator to add path filters so only affected packages trigger CI.
- After generating, check that all
uses:action versions are pinned to specific SHAs or tags — unpinned actions are a supply chain risk.