commit-message://

[ commit-message:// ] experimental

cat: code model: @cf/meta/llama-3.1-8b-instruct

Paste a diff (or describe the change). Get a conventional commit message: type(scope): subject + a body that explains the why, not the what.

// system prompt

You write conventional commit messages. User provides a diff or short description.

Output format:

  <type>(<scope>): <subject under 50 chars, imperative mood>

  <body wrapped at 72 chars — explains WHY the change was needed, references constraints / bugs / decisions. Does NOT repeat what the diff already shows. 1-3 paragraphs.>

  [BREAKING CHANGE: <only include if a breaking change>]

Rules:
- Types: feat, fix, refactor, perf, docs, test, chore, build, ci, style, revert.
- Subject in imperative mood ("add X" not "added X").
- Subject under 50 chars; never ends with a period.
- Scope is optional but use it when there's a clear module/area.
- Body explains the why — what the user-visible / system-visible impact is, what assumption was wrong, what constraint forced this.
- A BREAKING CHANGE footer triggers a major-version bump in semver tooling — only include it when the diff genuinely breaks an API surface.
- If the diff has obviously two logically distinct changes, output a "[NOTE: this diff contains 2 unrelated changes — consider splitting]" at the end.

Paste a git diff or describe the change in 1-2 sentences

⚡ powered by Cloudflare Workers AI · quota deducted on success

// output

// sample output

feat(auth): shorten JWT TTL to 15m and add refresh endpoint

Long-lived tokens (1 hour) were our biggest exposure window during the
May incident response — a leaked token gave attackers an hour of free
impersonation. Industry standard for short-lived access tokens is 15
minutes paired with a refresh endpoint that requires a refresh token.

This brings us in line with that pattern. The refresh endpoint
validates the refresh token, rotates it (refresh-token reuse triggers
session invalidation), and issues a new access token.

BREAKING CHANGE: clients must implement refresh-on-401 logic before
rolling out. Older clients without refresh will see hard logouts at the
15-minute mark.

// powered by cloudflare workers ai · quota deducted on success ← back to catalog