Create a Complete Code Review Checklist for Your Project
A prompt to generate an exhaustive code review checklist, adapted to your tech stack and business context, with concrete examples.
Paste in your AI
Paste this prompt in ChatGPT, Claude or Gemini and customize the variables in brackets.
Tu es un développeur senior spécialisé en assurance qualité logicielle avec 15 ans d'expérience en code review. Génère une checklist de code review complète et structurée pour un projet utilisant [LANGAGE/FRAMEWORK] dans le contexte suivant : [DESCRIPTION DU PROJET ET DE SON DOMAINE MÉTIER].
La checklist doit couvrir les catégories suivantes, avec pour chaque point un niveau de sévérité (bloquant, majeur, mineur) :
- Correction fonctionnelle : le code fait-il ce qu'il est censé faire ? Les edge cases sont-ils gérés ?
- Lisibilité et maintenabilité : nommage des variables/fonctions, complexité cyclomatique, respect des conventions du projet.
- Sécurité : injections, validation des entrées, gestion des secrets, failles OWASP Top 10 applicables.
- Performance : requêtes N+1, fuites mémoire, algorithmes sous-optimaux, mise en cache.
- Tests : couverture des cas nominaux et limites, qualité des assertions, indépendance des tests.
- Architecture : respect des principes SOLID, couplage, séparation des responsabilités.
- Gestion des erreurs : exceptions attrapées et traitées correctement, messages d'erreur explicites, logging.
- Documentation : docstrings sur les fonctions publiques, commentaires sur la logique complexe uniquement.
Pour chaque point de la checklist, fournis :
- La question à se poser lors de la review
- Un exemple concret de code problématique en [LANGAGE/FRAMEWORK]
- La version corrigée correspondante
- Le niveau de sévérité
Termine par une section "Red flags" listant les 5 signaux d'alerte qui doivent déclencher une review approfondie.
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 leverages the quality assurance expert role to produce a code review checklist that goes beyond superficial checks. By specifying your <strong>language or framework</strong>, you get code examples directly applicable to your project rather than generic advice.</p><p>The 8-category structure covers all critical review dimensions: from functional correctness to documentation, including security and performance. The <strong>severity level</strong> system (blocking, major, minor) helps prioritize feedback and avoids drowning the code author in cosmetic remarks when structural issues exist.</p><p>To get the most from this prompt, describe your business context precisely in the <strong>[PROJECT DESCRIPTION]</strong> variable: a banking API will not have the same security requirements as an internal tool. You can also iterate by asking to deepen a specific category after receiving the initial checklist.</p>
Use Cases
Expected Output
A structured checklist in 8 sections with a review question, a problematic code example, its correction, and a severity level for each point. Ends with a list of 5 priority red flags.
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 gagner du temps, commencez par personnaliser les red flags avec les anti-patrons récurrents de votre projet (ex : fuite de contexte, logs inutiles). Cela recentre la revue sur l’essentiel et évite une checklist générique trop longue.
📬 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.