Define a Git strategy for a team
Define a comprehensive 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 : 1. **Branching model** : recommande et compare Git Flow, GitHub Flow, Trunk-Based Development ou une variante adaptée à notre contexte. Justifie ton choix. 2. **Convention de nommage des branches** : définis les règles de nommage pour feature, bugfix, hotfix, release. 3. **Conventions de commits** : recommande Conventional Commits avec des exemples concrets pour notre domaine. 4. **Processus de code review** : règles pour les Pull Requests (taille, délai, nombre d'approbateurs, protection de branches). 5. **Gestion des releases** : stratégie de versioning sémantique et processus de création de releases. 6. **Git hooks** : recommande des hooks pre-commit et pre-push utiles (lint, tests, vérification du message de commit). 7. **Documentation** : fournis un CONTRIBUTING.md résumant toutes ces conventions.
Why this prompt works
<p>This prompt adopts a consultative rather than prescriptive approach: by asking for a comparison of branching models with justification for the recommended choice, it allows obtaining a recommendation adapted to the team's specific context rather than a universal recipe.</p><p>The description of current problems is a key element of this prompt because it allows the AI to diagnose root causes and recommend targeted solutions. For example, frequent conflicts may indicate branches with too long lifespans, pointing toward Trunk-Based Development.</p><p>The request for a CONTRIBUTING.md as the final deliverable is practical because it produces a document directly shareable with the team, reducing friction between the recommendation and its effective adoption.</p>
Use Cases
Expected Output
A comprehensive Git strategy with recommended branching model, commit conventions, PR rules and a ready-to-use CONTRIBUTING.md.
Learn more
Check the full skill on Prompt Guide to master this technique from A to Z.
View on Prompt GuideGlossary Terms
Similar Prompts
Learn the basics of Git for beginners
Learn Git from scratch with illustrated explanations, concrete examples, a practical workflow and a cheatsheet of essential commands.
Implement robust error handling in Node.js
Create a professional Node.js error handling architecture with custom error classes, centralized middleware and monitoring.
Write integration tests for an API
Create comprehensive API integration tests with database setup, authentication, CRUD and end-to-end scenarios.
Create an optimized Dockerfile for production
Create an optimized multi-stage Dockerfile for production with maximum security, lightweight image and best practices.