P
💻DeveloppementAdvancedAll AIs

Create a Complete Automated CI/CD Pipeline

This prompt generates a complete, customized CI/CD pipeline for your stack, covering build, tests, security and multi-environment deployment.

Paste in your AI

Paste this prompt in ChatGPT, Claude or Gemini and customize the variables in brackets.

Tu es un ingénieur DevOps senior spécialisé en CI/CD. Conçois une pipeline d'intégration et de déploiement continu complète pour mon projet.

Contexte du projet :

  • Langage / framework : [LANGAGE_ET_FRAMEWORK]
  • Plateforme CI/CD utilisée : [PLATEFORME_CI_CD] (ex : GitHub Actions, GitLab CI, Jenkins, CircleCI)
  • Environnements cibles : [ENVIRONNEMENTS] (ex : staging, production, preview par PR)
  • Infrastructure de déploiement : [INFRASTRUCTURE] (ex : AWS ECS, Kubernetes, VPS avec Docker, Vercel)
  • Base de données : [BASE_DE_DONNEES] (ex : PostgreSQL, MongoDB, aucune)

Ce que la pipeline doit inclure :

  1. Stage Build : Installation des dépendances, compilation, génération des artefacts. Inclus le cache des dépendances pour accélérer les builds.

  2. Stage Qualité : Linting (ESLint, Flake8, etc.), formatage (Prettier, Black), analyse statique du code. Échouer le pipeline si les standards ne sont pas respectés.

  3. Stage Tests :

    • Tests unitaires avec couverture de code (seuil minimum à définir)
    • Tests d'intégration avec services auxiliaires (base de données, Redis, etc.)
    • Tests end-to-end si applicable
  4. Stage Sécurité : Scan des dépendances (vulnérabilités connues), analyse SAST, vérification des secrets exposés.

  5. Stage Déploiement :

    • Déploiement automatique en staging sur merge dans develop
    • Déploiement en production sur merge dans main avec approbation manuelle
    • Stratégie de rollback en cas d'échec
  6. Notifications : Alertes sur échec (Slack, email ou autre) avec le contexte de l'erreur.

Pour chaque stage, fournis :

  • Le fichier de configuration complet (YAML ou autre selon la plateforme)
  • Les scripts auxiliaires nécessaires
  • Les variables d'environnement et secrets à configurer
  • Les bonnes pratiques spécifiques à ma stack

Ajoute également :

  • Un schéma visuel ASCII du flux de la pipeline
  • Les optimisations de performance (parallélisation, cache, matrices de build)
  • La gestion des branches (feature, develop, main, hotfix)
  • Un guide de dépannage pour les erreurs courantes

Personalize this prompt with Léa

Answer 3 questions and Léa tailors the prompt to your situation.

Why this prompt works

<p>This prompt is designed to produce a production-ready CI/CD pipeline in a single interaction. By entering your <strong>language, CI/CD platform, infrastructure and environments</strong>, you get a directly usable configuration tailored to your technical context.</p><p>The six-stage structure covers the entire delivery cycle: from initial build to deployment with automatic rollback. Each stage includes <strong>security best practices</strong> (vulnerability scanning, secrets detection) and <strong>quality</strong> (linting, test coverage), preventing you from missing critical steps.</p><p>For optimal results, be specific about your infrastructure: for example, state <strong>"GitHub Actions + Docker + AWS ECS Fargate"</strong> rather than just "cloud". The richer the context, the more operational the generated pipeline will be without modifications. Feel free to iterate by requesting adjustments to a specific stage after the initial generation.</p>

Use Cases

Set up a CI/CD pipeline for a new project from scratchModernize a manual deployment process to automated continuous deliveryAdd security and quality stages to an existing pipeline

Expected Output

A complete CI/CD configuration file (YAML), auxiliary scripts, a pipeline flow diagram, a list of environment variables to configure, and a best practices guide with common error troubleshooting.

Improve this prompt

Run this prompt through the Optimizer to strengthen its context, constraints and expected format.

Improve this prompt with the Optimizer

Comments

  • LéaAI

    Ajoutez un stage de déploiement à sec (dry-run) avant le vrai déploiement. Il exécute les scripts sans effectuer les mutations, validant la configuration et les secrets. Cela évite les rollbacks coûteux en production.

📬 Get new prompts every week

Join our newsletter and never miss a prompt.

Go further

Similar Prompts

💻DeveloppementIntermediateAll AIs

NetworkPolicies for micro-segmentation

Isolate workloads with network policies

061
💻DeveloppementIntermediateClaude

Prompt Claude to Create a Prototype

Creating a prototype is a crucial step in developing a product, application, or service. Traditionally, this phase requires a variety of technical skills, time, and often a multidisciplinary team. With Claude, you can significantly accelerate this process by generating functional prototypes from a simple description of your idea. Whether you want to design an interactive user interface, a web application mockup, an API prototype, or even a technical proof of concept, Claude can produce functional code, HTML/CSS wireframes, or complete architectures ready to be tested. The major advantage is Claude's ability to iterate quickly: you describe your vision, get a first prototype, then refine through successive exchanges until you get exactly what you're looking for. This approach democratizes rapid prototyping and allows entrepreneurs, designers, and product managers to validate their hypotheses without fully relying on a development team in the early stages of the project.

093
💻DeveloppementAdvancedChatGPT

Optimize Slow SQL Queries

Analyze and optimize your slow SQL queries through execution plan analysis and precise index recommendations.

38344
💻DeveloppementIntermediateAll AIs

Sora Prompt for Debugging Code

Sora, OpenAI's video generation model, may seem like a surprising choice for debugging code. Yet its ability to produce dynamic visualizations opens up unique perspectives for understanding and resolving complex bugs. By generating visual representations of execution flow, data structures, or interactions between components, Sora allows developers to literally see their code's behavior. This visual approach is particularly effective for bugs related to user interfaces, animations, state transitions, or rendering issues. Instead of sifting through endless logs, you can ask Sora to create a video illustrating expected versus observed behavior, making problem identification easier. The prompts on this page guide you in using Sora for debugging, turning textual bug descriptions into clear visualizations that accelerate resolution. Whether you're working on front-end, visual algorithms, or complex data flows, these techniques help you adopt a visual debugging approach.

063