AI CodingThrive Editorial

50 prompts d’IA pour les développeurs

Un bon prompt de programmation décrit le comportement actuel, la modification attendue et les critères de réussite. Fournissez à l’assistant une petite partie du dépôt et demandez un diff que vous pourrez tester.

25 min de lectureMise à jour
Espace de travail de développeur avec un ordinateur portable et un fil orange reliant les tâches de programmation.

La version courte

  • Un bon prompt de programmation décrit le comportement actuel, la modification attendue et les critères de réussite. Fournissez à l’assistant une petite partie du dépôt et demandez un diff que vous pourrez tester.
  • Ne transmettez jamais d’identifiants, de données client privées ou de dépôts propriétaires complets à un assistant non autorisé. Exécutez les commandes et les tests proposés dans votre environnement. Un correctif plausible ne prouve pas que la modification fonctionne.

Un bon prompt de programmation décrit le comportement actuel, la modification attendue et les critères de réussite. Fournissez à l’assistant une petite partie du dépôt et demandez un diff que vous pourrez tester.

Ne transmettez jamais d’identifiants, de données client privées ou de dépôts propriétaires complets à un assistant non autorisé. Exécutez les commandes et les tests proposés dans votre environnement. Un correctif plausible ne prouve pas que la modification fonctionne.

Comment utiliser cette collection

Choisissez la tâche la plus proche de votre travail. Copiez le prompt, remplacez la scène ou le contexte générique par vos informations et conservez les contraintes utiles pour évaluer le résultat. Modifiez une variable à la fois afin d’identifier ce qui s’améliore.

Cette méthode reprend les recommandations du guide de prompt engineering de GitHub Copilot : fournir un contexte précis et vérifier la réponse, sans supposer qu’un premier résultat soigné est correct.

Prompts de diagnostic

Cette série porte sur le diagnostic. Fournissez votre code et votre commande de test avant de valider la réponse.

1. Un analyseur de dates défaillant

Help with a failing date parser in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then state competing hypotheses, request a minimal reproduction and identify evidence that separates them. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.

Vérification : Exécutez le scénario de reproduction proposé avant d’appliquer un correctif.

2. Une requête de base de données lente

Help with a slow database query in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then state competing hypotheses, request a minimal reproduction and identify evidence that separates them. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.

Vérification : Exécutez le scénario de reproduction proposé avant d’appliquer un correctif.

3. Un formulaire envoyé plusieurs fois

Help with a form with duplicate submissions in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then state competing hypotheses, request a minimal reproduction and identify evidence that separates them. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.

Vérification : Exécutez le scénario de reproduction proposé avant d’appliquer un correctif.

4. Une API aux erreurs incohérentes

Help with an API with inconsistent errors in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then state competing hypotheses, request a minimal reproduction and identify evidence that separates them. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.

Vérification : Exécutez le scénario de reproduction proposé avant d’appliquer un correctif.

5. Un cas limite de pagination

Help with a pagination edge case in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then state competing hypotheses, request a minimal reproduction and identify evidence that separates them. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.

Vérification : Exécutez le scénario de reproduction proposé avant d’appliquer un correctif.

6. Un test d’intégration instable

Help with a flaky integration test in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then state competing hypotheses, request a minimal reproduction and identify evidence that separates them. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.

Vérification : Exécutez le scénario de reproduction proposé avant d’appliquer un correctif.

7. Une limite de téléversement de fichiers

Help with a file upload limit in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then state competing hypotheses, request a minimal reproduction and identify evidence that separates them. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.

Vérification : Exécutez le scénario de reproduction proposé avant d’appliquer un correctif.

8. Un bug d’invalidation du cache

Help with a cache invalidation bug in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then state competing hypotheses, request a minimal reproduction and identify evidence that separates them. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.

Vérification : Exécutez le scénario de reproduction proposé avant d’appliquer un correctif.

9. Une boucle de nouvelles tentatives dans une file

Help with a queue retry loop in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then state competing hypotheses, request a minimal reproduction and identify evidence that separates them. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.

Vérification : Exécutez le scénario de reproduction proposé avant d’appliquer un correctif.

10. Un contrôle d’autorisation

Help with an authorization check in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then state competing hypotheses, request a minimal reproduction and identify evidence that separates them. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.

Vérification : Exécutez le scénario de reproduction proposé avant d’appliquer un correctif.

Prompts de mise en œuvre

Cette série porte sur la mise en œuvre. Fournissez votre code et votre commande de test avant de valider la réponse.

11. Un analyseur de dates défaillant

Help with a failing date parser in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then make the smallest change that satisfies the stated behavior and show a focused diff. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.

Vérification : Vérifiez que le diff ne contient ni modification hors sujet ni accès aux données non prévu.

12. Une requête de base de données lente

Help with a slow database query in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then make the smallest change that satisfies the stated behavior and show a focused diff. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.

Vérification : Vérifiez que le diff ne contient ni modification hors sujet ni accès aux données non prévu.

13. Un formulaire envoyé plusieurs fois

Help with a form with duplicate submissions in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then make the smallest change that satisfies the stated behavior and show a focused diff. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.

Vérification : Vérifiez que le diff ne contient ni modification hors sujet ni accès aux données non prévu.

14. Une API aux erreurs incohérentes

Help with an API with inconsistent errors in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then make the smallest change that satisfies the stated behavior and show a focused diff. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.

Vérification : Vérifiez que le diff ne contient ni modification hors sujet ni accès aux données non prévu.

15. Un cas limite de pagination

Help with a pagination edge case in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then make the smallest change that satisfies the stated behavior and show a focused diff. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.

Vérification : Vérifiez que le diff ne contient ni modification hors sujet ni accès aux données non prévu.

16. Un test d’intégration instable

Help with a flaky integration test in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then make the smallest change that satisfies the stated behavior and show a focused diff. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.

Vérification : Vérifiez que le diff ne contient ni modification hors sujet ni accès aux données non prévu.

17. Une limite de téléversement de fichiers

Help with a file upload limit in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then make the smallest change that satisfies the stated behavior and show a focused diff. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.

Vérification : Vérifiez que le diff ne contient ni modification hors sujet ni accès aux données non prévu.

Visual example of a developer isolating a failing parser, making a focused change and running a check.

18. Un bug d’invalidation du cache

Help with a cache invalidation bug in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then make the smallest change that satisfies the stated behavior and show a focused diff. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.

Vérification : Vérifiez que le diff ne contient ni modification hors sujet ni accès aux données non prévu.

19. Une boucle de nouvelles tentatives dans une file

Help with a queue retry loop in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then make the smallest change that satisfies the stated behavior and show a focused diff. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.

Vérification : Vérifiez que le diff ne contient ni modification hors sujet ni accès aux données non prévu.

20. Un contrôle d’autorisation

Help with an authorization check in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then make the smallest change that satisfies the stated behavior and show a focused diff. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.

Vérification : Vérifiez que le diff ne contient ni modification hors sujet ni accès aux données non prévu.

Prompts de test des limites

Cette série porte sur les tests de limites. Fournissez votre code et votre commande de test avant de valider la réponse.

21. Un analyseur de dates défaillant

Help with a failing date parser in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then add unit or integration cases for empty, invalid and concurrent inputs as appropriate. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.

Vérification : Exécutez les tests et, si possible, vérifiez qu’ils échouent avant le correctif.

22. Une requête de base de données lente

Help with a slow database query in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then add unit or integration cases for empty, invalid and concurrent inputs as appropriate. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.

Vérification : Exécutez les tests et, si possible, vérifiez qu’ils échouent avant le correctif.

23. Un formulaire envoyé plusieurs fois

Help with a form with duplicate submissions in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then add unit or integration cases for empty, invalid and concurrent inputs as appropriate. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.

Vérification : Exécutez les tests et, si possible, vérifiez qu’ils échouent avant le correctif.

24. Une API aux erreurs incohérentes

Help with an API with inconsistent errors in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then add unit or integration cases for empty, invalid and concurrent inputs as appropriate. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.

Vérification : Exécutez les tests et, si possible, vérifiez qu’ils échouent avant le correctif.

25. Un cas limite de pagination

Help with a pagination edge case in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then add unit or integration cases for empty, invalid and concurrent inputs as appropriate. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.

Vérification : Exécutez les tests et, si possible, vérifiez qu’ils échouent avant le correctif.

26. Un test d’intégration instable

Help with a flaky integration test in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then add unit or integration cases for empty, invalid and concurrent inputs as appropriate. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.

Vérification : Exécutez les tests et, si possible, vérifiez qu’ils échouent avant le correctif.

27. Une limite de téléversement de fichiers

Help with a file upload limit in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then add unit or integration cases for empty, invalid and concurrent inputs as appropriate. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.

Vérification : Exécutez les tests et, si possible, vérifiez qu’ils échouent avant le correctif.

28. Un bug d’invalidation du cache

Help with a cache invalidation bug in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then add unit or integration cases for empty, invalid and concurrent inputs as appropriate. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.

Vérification : Exécutez les tests et, si possible, vérifiez qu’ils échouent avant le correctif.

29. Une boucle de nouvelles tentatives dans une file

Help with a queue retry loop in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then add unit or integration cases for empty, invalid and concurrent inputs as appropriate. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.

Vérification : Exécutez les tests et, si possible, vérifiez qu’ils échouent avant le correctif.

30. Un contrôle d’autorisation

Help with an authorization check in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then add unit or integration cases for empty, invalid and concurrent inputs as appropriate. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.

Vérification : Exécutez les tests et, si possible, vérifiez qu’ils échouent avant le correctif.

Prompts de revue de sécurité

Cette série porte sur la revue de sécurité. Fournissez votre code et votre commande de test avant de valider la réponse.

31. Un analyseur de dates défaillant

Help with a failing date parser in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then inspect authorization, input validation, error disclosure and rollback behavior. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.

Vérification : Vérifiez les affirmations de sécurité dans les routes et les règles de la base de données.

32. Une requête de base de données lente

Help with a slow database query in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then inspect authorization, input validation, error disclosure and rollback behavior. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.

Vérification : Vérifiez les affirmations de sécurité dans les routes et les règles de la base de données.

33. Un formulaire envoyé plusieurs fois

Help with a form with duplicate submissions in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then inspect authorization, input validation, error disclosure and rollback behavior. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.

Vérification : Vérifiez les affirmations de sécurité dans les routes et les règles de la base de données.

34. Une API aux erreurs incohérentes

Help with an API with inconsistent errors in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then inspect authorization, input validation, error disclosure and rollback behavior. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.

Vérification : Vérifiez les affirmations de sécurité dans les routes et les règles de la base de données.

Three-step code workflow: brief the work, inspect the result, edit and verify.

35. Un cas limite de pagination

Help with a pagination edge case in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then inspect authorization, input validation, error disclosure and rollback behavior. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.

Vérification : Vérifiez les affirmations de sécurité dans les routes et les règles de la base de données.

36. Un test d’intégration instable

Help with a flaky integration test in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then inspect authorization, input validation, error disclosure and rollback behavior. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.

Vérification : Vérifiez les affirmations de sécurité dans les routes et les règles de la base de données.

37. Une limite de téléversement de fichiers

Help with a file upload limit in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then inspect authorization, input validation, error disclosure and rollback behavior. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.

Vérification : Vérifiez les affirmations de sécurité dans les routes et les règles de la base de données.

38. Un bug d’invalidation du cache

Help with a cache invalidation bug in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then inspect authorization, input validation, error disclosure and rollback behavior. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.

Vérification : Vérifiez les affirmations de sécurité dans les routes et les règles de la base de données.

39. Une boucle de nouvelles tentatives dans une file

Help with a queue retry loop in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then inspect authorization, input validation, error disclosure and rollback behavior. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.

Vérification : Vérifiez les affirmations de sécurité dans les routes et les règles de la base de données.

40. Un contrôle d’autorisation

Help with an authorization check in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then inspect authorization, input validation, error disclosure and rollback behavior. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.

Vérification : Vérifiez les affirmations de sécurité dans les routes et les règles de la base de données.

Prompts de documentation pour la reprise du travail

Cette série porte sur la documentation nécessaire à la reprise du travail. Fournissez votre code et votre commande de test avant de valider la réponse.

41. Un analyseur de dates défaillant

Help with a failing date parser in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then write a concise changelog, usage example and rollback note tied to the implementation. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.

Vérification : Supprimez les affirmations qui n’ont été ni mesurées ni testées.

42. Une requête de base de données lente

Help with a slow database query in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then write a concise changelog, usage example and rollback note tied to the implementation. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.

Vérification : Supprimez les affirmations qui n’ont été ni mesurées ni testées.

43. Un formulaire envoyé plusieurs fois

Help with a form with duplicate submissions in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then write a concise changelog, usage example and rollback note tied to the implementation. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.

Vérification : Supprimez les affirmations qui n’ont été ni mesurées ni testées.

44. Une API aux erreurs incohérentes

Help with an API with inconsistent errors in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then write a concise changelog, usage example and rollback note tied to the implementation. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.

Vérification : Supprimez les affirmations qui n’ont été ni mesurées ni testées.

45. Un cas limite de pagination

Help with a pagination edge case in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then write a concise changelog, usage example and rollback note tied to the implementation. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.

Vérification : Supprimez les affirmations qui n’ont été ni mesurées ni testées.

46. Un test d’intégration instable

Help with a flaky integration test in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then write a concise changelog, usage example and rollback note tied to the implementation. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.

Vérification : Supprimez les affirmations qui n’ont été ni mesurées ni testées.

47. Une limite de téléversement de fichiers

Help with a file upload limit in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then write a concise changelog, usage example and rollback note tied to the implementation. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.

Vérification : Supprimez les affirmations qui n’ont été ni mesurées ni testées.

48. Un bug d’invalidation du cache

Help with a cache invalidation bug in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then write a concise changelog, usage example and rollback note tied to the implementation. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.

Vérification : Supprimez les affirmations qui n’ont été ni mesurées ni testées.

49. Une boucle de nouvelles tentatives dans une file

Help with a queue retry loop in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then write a concise changelog, usage example and rollback note tied to the implementation. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.

Vérification : Supprimez les affirmations qui n’ont été ni mesurées ni testées.

50. Un contrôle d’autorisation

Help with an authorization check in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then write a concise changelog, usage example and rollback note tied to the implementation. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.

Vérification : Supprimez les affirmations qui n’ont été ni mesurées ni testées.

Que vérifier avant d’utiliser le résultat

Ne transmettez jamais d’identifiants, de données client privées ou de dépôts propriétaires complets à un assistant non autorisé. Exécutez les commandes et les tests proposés dans votre environnement. Un correctif plausible ne prouve pas que la modification fonctionne.

Si le résultat ne répond pas à la tâche, raccourcissez le prompt et précisez l’information ou la contrainte manquante. Conservez la version utilisée pour pouvoir reproduire le visuel final ou la modification du code.

Pour aller plus loin

Vous avez une question ou une correction?

Contacter Thrive

Continuez à lire

Pour en savoir plus sur le journal

Tous les articles