Commit Message Generator

CategoryGeneral
Authormehmetalicayhan
LicenseMIT
Rating4.50/5
Uses19.1K

What it does

Standardize your project history by automating the creation of Conventional Commits. Instead of spending time debating whether a change is a feat or a fix, you provide the raw task details and a ticket prefix, and you get a clean, industry-standard commit message instantly. This is particularly useful in team environments where a strict changelog is required for automated versioning (like Semantic Release) or when you're managing multiple Jira/Linear tickets and need to ensure every commit is correctly mapped to a task ID without manual formatting errors.

Use cases

  • Ticket-based workflows: Converting a Jira ticket description and ID into a formatted commit like feat(UI-123): implement dark mode toggle.
  • Rapid prototyping: Quickly summarizing several small changes into a single, professionally formatted commit message before pushing to a remote branch.
  • Legacy cleanup: Rewriting messy commit histories during an interactive rebase to meet a project's contribution guidelines.
  • CI/CD automation: Ensuring all commit messages follow a pattern that triggers the correct version bump (patch, minor, or major).

How to use

Provide the AI with the task description and the required ticket prefix. For the best results, be specific about what changed in the code.
text
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.

Tips

  • Provide context: Instead of saying "fixed bug," say "fixed null pointer exception in the UserAuth service" to get a more descriptive commit body.
  • Specify the scope: If you want the commit to include a scope (e.g., feat(api): ...), mention the specific module or component you worked on.
  • Batch your updates: If you've made multiple related changes, list them as bullet points so the AI can synthesize them into a concise summary.
  • Define the type: If the AI is miscategorizing a refactor as a feat, explicitly tell it the type of change you made.

Notes

  • Verification required: Always review the generated message to ensure the "type" (feat, fix, chore, etc.) accurately reflects the code change.
  • Format strictness: Since the prompt suppresses explanations, it won't tell you *why* it chose a specific conventional commit type.
Join our Telegram