Define a Git Strategy for a Team
Define a complete Git strategy adapted to your team: branching model, conventions, code review, and release management.
Paste in your AI
Paste this prompt in ChatGPT, Claude or Gemini and customize the variables in brackets.
Tu es un ingénieur principal expérimenté en gestion de projets logiciels avec Git. Je dois définir une stratégie Git complète pour mon équipe.
Contexte de l'équipe :
- Taille : [EX: 5 développeurs, 2 seniors + 3 juniors]
- Type de projet : [EX: SaaS web, application mobile, librairie open-source]
- Fréquence de déploiement : [EX: plusieurs fois par jour, releases hebdomadaires]
- Environnements : [EX: dev, staging, production]
- Outils actuels : [EX: GitHub, GitLab, Bitbucket]
Problèmes actuels :
[DÉCRIRE_LES_PROBLÈMES: ex. conflits fréquents, historique Git illisible, déploiements chaotiques]
Conseille-moi sur une stratégie Git complète en couvrant :
- Branching model : recommande et compare Git Flow, GitHub Flow, Trunk-Based Development ou une variante adaptée à notre contexte. Justifie ton choix.
- Convention de nommage des branches : définis les règles de nommage pour feature, bugfix, hotfix, release.
- Conventions de commits : recommande Conventional Commits avec des exemples concrets pour notre domaine.
- Processus de code review : règles pour les Pull Requests (taille, délai, nombre d'approbateurs, protection de branches).
- Gestion des releases : stratégie de versioning sémantique et processus de création de releases.
- Git hooks : recommande des hooks pre-commit et pre-push utiles (lint, tests, vérification du message de commit).
- Documentation : fournis un CONTRIBUTING.md résumant toutes ces conventions.
Personalize this prompt with Léa
Léa rewrites this prompt for your job and your exact goal — 3 quick questions.
Why this prompt works
<p>This prompt takes a consultative rather than prescriptive approach: by requesting a comparison of branching models with a justified recommendation, it provides a recommendation adapted to the team's specific context rather than a universal recipe.</p><p>Describing current problems is a key element of this prompt as it allows the AI to diagnose root causes and recommend targeted solutions. For example, frequent conflicts may indicate overly long-lived branches, pointing toward Trunk-Based Development.</p><p>Requesting a CONTRIBUTING.md as the final deliverable is practical as it produces a document directly shareable with the team, reducing friction between the recommendation and its effective adoption.</p>
Use Cases
Expected Output
A complete Git strategy with recommended branching model, commit conventions, PR rules, and a ready-to-use CONTRIBUTING.md.
Improve this prompt
Run this prompt through the Optimizer to strengthen its context, constraints and expected format.
Improve this prompt with the OptimizerComments
- LéaAI
Pour des juniors, préférez GitHub Flow ou Trunk-Based Development plutôt que Git Flow : moins de branches = moins de complexité. Ajoutez un hook pre-commit qui vérifie le format du message de commit (via commitlint) pour imposer les Conventional Commits dès le départ.
📬 Get new prompts every week
Join our newsletter and never miss a prompt.
Go further
Similar Prompts
Sora Prompt for Creating E2E Tests
End-to-end (E2E) tests are essential for ensuring application reliability, but writing them remains time-consuming and repetitive. Sora, thanks to its advanced generation capabilities, makes it possible to automate the creation of complete E2E test scenarios in seconds. By formulating a precise prompt describing user journeys, expected interactions, and validation criteria, you obtain structured test suites covering nominal cases as well as edge cases. The prompt engineering approach applied to Sora transforms how QA and development teams approach test coverage. Instead of starting from a blank page, you describe the expected behavior of your application in natural language, and Sora generates the corresponding test code with appropriate assertions. This method significantly reduces the time needed to set up an E2E suite while maintaining a professional quality level. Whether you use Playwright, Cypress, or Selenium, the prompts presented here adapt to your technical stack and the complexity of your application.
Implement rate limiting
Protect APIs from abuse
GitHub Copilot Prompt for Creating a REST API
GitHub Copilot has become an essential assistant for developers looking to accelerate the creation of REST APIs. Thanks to its direct integration into the code editor, it understands the context of your project and generates structured code in real time. Whether you work with Node.js and Express, Python and FastAPI, or Java and Spring Boot, Copilot adapts to your tech stack to produce endpoints conforming to REST conventions. The main challenge lies in formulating the prompt: a well-structured prompt yields a complete API with data validation, error handling, authentication, and documentation. A vague prompt, on the other hand, will produce generic code requiring many adjustments. In this guide, we offer an optimized prompt that fully leverages GitHub Copilot's capabilities to generate a professional, testable, production-ready REST API. You will also discover variants adapted to your experience level as well as practical tips to get the most out of this tool on a daily basis.
GitHub Copilot Prompt for Creating E2E Tests
End-to-end (E2E) tests are essential for validating the overall functionality of an application, but writing them is often time-consuming and repetitive. GitHub Copilot, integrated directly into your code editor, can significantly speed up this process by generating comprehensive test scenarios from natural language descriptions. Whether you use Playwright, Cypress, or Selenium, Copilot understands the context of your project—components, routes, selectors—to produce realistic and maintainable tests. The challenge is to craft prompts precise enough to obtain tests that cover critical user journeys, handle wait states and assertions robustly, while respecting your testing framework's best practices. In this guide, you will find an optimized main prompt as well as variants adapted to your experience level to get the most out of GitHub Copilot in creating your E2E tests.