Conventional commit message generator

Generates a Conventional Commits message from a diff or a plain description, picking the right type and scope, using imperative mood, and flagging breaking changes correctly.

PLPromptByte Library@promptbytePublished Jun 25

TextCoding #commit message #conventional commits #git

Version 1 of 1 · published Jun 25, 2026Version 1 · only version

Example output

See all results

Anthropic · Claude Sonnet 5 PLPromptByte Library Version 1

Prompt

Version 1 · 2 variables · 1 required

Fill in the values below — the customized prompt updates as you type. marks a required value.

Diff or description of changes{{changes}}

Paste git --no-pager diff --staged output, or just describe what you changed and why.

Issue or ticket reference(optional){{refs}}

Issue number or ticket id for the Refs footer. Leave blank if there is none.

Fill in Diff or description of changes to copy the customized prompt.

Resultsfor version 1

All models Claude Sonnet 51

Version 1 · only version

Claude Sonnet 5 result by PromptByte Library
Anthropic · Claude Sonnet 5 PLPromptByte Library (@promptbyte)Version 1Published Jun 25
Compare
fix(auth)!: reject refresh tokens issued before a password change Refresh tokens were validated only against their signature and expiry, so a token minted before a password reset stayed usable for its full thirty-day lifetime. Anyone holding a captured token kept access after the account owner rotated their credentials, which is precisely the scenario a password reset is meant to close. The user row now carries credentials_changed_at, and verifyRefreshToken compares the token's iat claim against it. Tokens issued at or before that timestamp are rejected with TOKEN_SUPERSEDED, a distinct…
Community submittedFull output
Settings: Unknown
Open result

Showing all 1 public result from Claude Sonnet 5 on version 1.

Usage notes

Paste either git --no-pager diff --staged output or a plain-English description of what you did. Both work; the diff gives a more accurate type and scope.

The original prompt ends with a throwaway opening line ("I need help generating a commit message for my recent changes"). That has been replaced with the two input fields, and a line pinning subject and body widths has been added — without it the model tends to produce a 90-character subject that git tooling truncates awkwardly.

Check the type before committing. Models reach for feat when a change adds a code path even if that path only fixes a bug, and for refactor when behaviour actually changed. The type drives semantic-release version bumps, so a wrong one has consequences beyond the log.

The ! marker and BREAKING CHANGE: footer are redundant by the spec — either signals a breaking change. Using both, as in the sample below, is legal and some teams prefer it for visibility.

Attribution: adapted from https://github.com/f/awesome-chatgpt-prompts by jeff-nasseri, licensed CC0-1.0. Source file: https://github.com/f/awesome-chatgpt-prompts/blob/main/PROMPTS.md

Conventional commit message generator

Example output

Prompt

Resultsfor version 1

Models represented

Something wrong with this prompt?

Plan an incremental library migration with rollback checkpoints

Plan a representative load test with clear stop conditions

Review HTML for actionable accessibility issues

Build a focused STRIDE threat model for a feature

Design an API client with bounded retries and timeouts

Triage a slow SQL query using its real execution plan

Discussion 0

Example output

Prompt

Resultsfor version 1

Models represented

Something wrong with this prompt?

Related prompts

Plan an incremental library migration with rollback checkpoints

Plan a representative load test with clear stop conditions

Review HTML for actionable accessibility issues

Build a focused STRIDE threat model for a feature

Design an API client with bounded retries and timeouts

Triage a slow SQL query using its real execution plan

Discussion 0