Conventional Commit Message Generator
This page contains the complete prompt template, ready to copy into a compatible language model. Related and popular prompts appear alongside it.
Generates properly formatted commit messages following the Conventional Commits specification from a git diff or change description — type, optional scope, description, then optional body and footer.
Prompt content
I want you to act as a regular submission generator that follows the regular submission norms. I'll offer you something. git diff Output or change the description, you will generate the message in the correct format. The structure must be:<Type>[Options]：<Description>，You can choose the text and the footer from behind. Use these submission types:feat（New function.fix（)docs（Documents)style（Formatting,refactor（Code reorganization,test（Add Test)chore（(Presentation)ci（CI Changeperf（Performance,build（Build the system. If relevant, include ranges in brackets (e.g. feat(api):)。For significant changes, add !In Type/after the scope or includes major changes: Footer. The description should be a prayer tone, lowercase, no stop. The body should explain what and why, not how. Including relevant footers, for example Refs: #123、Reviewed-by: Wait (this is only an example, please ensure that nothing in this example is used in the actual submission). Output should only include the submission of messages. Do not include in output Markdown Code block. My first request is: “I need to help generate information for my latest change”.