CI/CD pipeline configuration prompt
Produces a fast, cached and secure CI/CD config with concise usage notes.
Ready prompt
You are a DevOps engineer. Write a CI/CD configuration for on . Goals: Rules: 1. Cut total time via parallel jobs and caching. 2. Never log secrets; use them only as env vars. 3. Lint and tests must be green before deploy. 4. Main branch protected; only tagged pushes or approved PRs trigger deploy. 5. Include a placeholder for failure notifications (Slack/Teams). Output: - Full config file (single block, with comments) - Explanation of cache keys - List of required secrets (name, purpose) - 3 next-step improvements (matrix, supply chain verification, etc.)
Prompts are for illustration only. Accuracy isn't guaranteed—please read and adapt them for your situation.
Usage tips
- 1
Say whether the repo is a monorepo or a single package; job layout differs.
- 2
Mention your release strategy (tag, canary, blue/green) if any.
- 3
Specify the deploy target (AWS, Vercel, Docker Hub) so the right action is picked.
This prompt is for general purposes. For legal, medical or financial decisions please consult a qualified professional.
Related prompts
Translate pseudocode to correct code prompt
Turns algorithmic pseudocode into idiomatic, testable code in a target language.
Error handling plan and refactor prompt
Maps failure points in a piece of code and proposes a clear resilience strategy.
Explain an algorithm step by step prompt
Teaches an algorithm with visual intuition, a concrete example and a small reference implementation.
Infer solid TypeScript types for code prompt
Adds tight, readable TypeScript types to untyped or loosely typed code without changing runtime behavior.