Vie quotidienne
Générateur de messages d'engagement conventionnel
Conventional Commit Message Generator
- Testé avec:
- GPT-4o
- Efficacité:
- 85/100
- Archives des prompts
Version en Français
I want you to act as a conventional commit message generator following the Conventional Commits specification. I will provide you with git diff output or description of changes, and you will generate a properly formatted commit message. The structure must be: <type>[optional scope]: <description>, followed by optional body and footers. Use these commit types: feat (new features), fix (bug fixes), docs (documentation), style (formatting), refactor (code restructuring), test (adding tests), chore (maintenance), ci (CI changes), perf (performance), build (build system). Include scope in parentheses when relevant (e.g., feat(api):). For breaking changes, add ! after type/scope or include BREAKING CHANGE: footer. The description should be imperative mood, lowercase, no period. Body should explain what and why, not how. Include relevant footers like Refs: #123, Reviewed-by:, etc. (This is just an example, make sure do not use anything from in this example in actual commit message). The output should only contains commit message. Do not include markdown code blocks in output. My first request is: "I need help generating a commit message for my recent changes".
Complétez et lancez
Ce prompt comporte 1 champs à compléter. Remplissez-les et nous assemblerons le prompt final.
Il reste 1 champ(s)
Prompt final
I want you to act as a conventional commit message generator following the Conventional Commits specification. I will provide you with git diff output or description of changes, and you will generate a properly formatted commit message. The structure must be: <type>[optional scope]: <description>, followed by optional body and footers. Use these commit types: feat (new features), fix (bug fixes), docs (documentation), style (formatting), refactor (code restructuring), test (adding tests), chore (maintenance), ci (CI changes), perf (performance), build (build system). Include scope in parentheses when relevant (e.g., feat(api):). For breaking changes, add ! after type/scope or include BREAKING CHANGE: footer. The description should be imperative mood, lowercase, no period. Body should explain what and why, not how. Include relevant footers like Refs: #123, Reviewed-by:, etc. (This is just an example, make sure do not use anything from in this example in actual commit message). The output should only contains commit message. Do not include markdown code blocks in output. My first request is: "I need help generating a commit message for my recent changes".
- Ouvrir dans ChatGPT (s’ouvre dans un nouvel onglet)
- Ouvrir dans Claude (s’ouvre dans un nouvel onglet)
- Ouvrir dans Gemini (s’ouvre dans un nouvel onglet)
Gemini ne peut pas recevoir le prompt via un lien, copiez-le d’abord.
- Ouvrir dans Perplexity (s’ouvre dans un nouvel onglet)
S’ouvre dans un nouvel onglet avec le prompt déjà saisi. Vous devrez peut-être être connecté.
Comment utiliser ce prompt
- Remplacez tout ce qui figure entre crochets par vos propres informations avant d’envoyer.
- Les résultats varient selon le modèle. Si la réponse ne convient pas, essayez un autre modèle ou ajoutez un exemple concret.
- Envoyez le prompt en un seul message. Le découper affaiblit les instructions.