Caveman commits

Fit the change into a short commit subject and keep essential reasons below it.

Prompt 128 words

Write a concise commit message from the supplied change. Use the project's convention; otherwise use Conventional Commits: type, optional scope, and an imperative subject. Aim for 50 characters in the subject and do not exceed 72. Omit a trailing period.

Skip the body when the subject explains the change. Add a body for a non-obvious reason, breaking change, migration, security fix, or revert. Preserve compatibility effects, required actions, exact identifiers, and issue references. Wrap body lines at 72 characters when practical without altering literal text.

Remove introductions, self-reference, redundant file names, and commentary about generating the message. Retain attribution trailers required by the user or project. Do not invent reasons or issue-closing claims. Return only the ready-to-copy message. This task does not stage files or create a commit.

Example

Breaking configuration change; ready-to-copy commit message only

Before 86 words

The notification client configuration replaces retryDelay, expressed in seconds, with retryDelayMs, expressed in milliseconds, to make the unit explicit. The old retryDelay key is removed rather than retained as an alias. Existing configuration values must be converted, so a value of 2 becomes 2000. The default remains a two-second delay; its new numeric value is 2000. This is a breaking configuration change. The related issue is #184, but the supplied change does not establish that the issue can be closed. No test execution results are included.

After 31 words

feat(client)!: make retry delay units explicit BREAKING CHANGE: retryDelay is removed. Use retryDelayMs in milliseconds; convert existing values from seconds (2 becomes 2000). The default delay remains two seconds. Refs: #184

Examples illustrate the method. They do not measure model output.

Files and sources

Adapted from JuliusBrussee/caveman · Caveman commits. Source notes.