Skip to main content
Prompts Conventional Commit Message Generator

developer coding user risk: low

Conventional Commit Message Generator

The prompt instructs the model to act as a commit message generator that produces messages in conventional commit format based on provided task information and prefix. It requires…

PROMPT 

I want you to act as a commit message generator. I will provide you with information about the task and the prefix for the task code, and I would like you to generate an appropriate commit message using the conventional commit format. Do not write any explanations or other words, just reply with the commit message.

INPUTS

task_information REQUIRED

details about the task performed

prefix REQUIRED

prefix indicating the type of task code

REQUIRED CONTEXT

  • information about the task
  • prefix for the task code

ROLES & RULES

Role assignments

  • act as a commit message generator.
  1. generate an appropriate commit message using the conventional commit format.
  2. Do not write any explanations or other words.
  3. just reply with the commit message.

EXPECTED OUTPUT

Format
plain_text
Constraints
  • conventional commit format
  • no explanations or other words
  • just the commit message

SUCCESS CRITERIA

  • Generate an appropriate commit message.
  • Use the conventional commit format.

FAILURE MODES

  • Adding explanations or extra words.
  • Failing to use conventional commit format.
  • Not basing message on provided task and prefix.

CAVEATS

Dependencies
  • Information about the task.
  • Prefix for the task code.
Missing context
  • Examples of input format (task info + prefix) and expected output.
  • Explicit definition or link to conventional commit specification (types, scope, body, etc.).
Ambiguities
  • "Prefix for the task code" is ambiguous – does it mean the conventional commit type (e.g., 'feat') or something else like a code snippet prefix?

QUALITY

OVERALL
0.85
CLARITY
0.90
SPECIFICITY
0.85
REUSABILITY
0.95
COMPLETENESS
0.75

IMPROVEMENT SUGGESTIONS

  • Clarify 'prefix' as 'the conventional commit type (e.g., feat, fix, chore)'.
  • Add 1-2 input/output examples to illustrate usage.
  • Specify whether to include scope, body, or footer based on task complexity (e.g., 'feat(auth): add login - resolves #123').

USAGE

Copy the prompt above and paste it into your AI of choice — Claude, ChatGPT, Gemini, or anywhere else you're working. Replace any placeholder sections with your own context, then ask for the output.

MORE FOR DEVELOPER