---
name: caveman-commit
description: "Fit the change into a short commit subject and keep essential reasons below it. Use for Commit messages, Breaking changes, Migration commits."
license: MIT
---

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.