yigityildiz0 Caveman Commit
Draft the message only. Do not stage, commit, amend, push, or change files.
Safety-adapted from JuliusBrussee/caveman, MIT licensed. Preserve the included LICENSE when redistributing.
Workflow
- Inspect the relevant diff and recent commit convention when available.
- Identify the change type, scope, user-visible effect, and non-obvious why.
- Draft the shortest message that preserves those facts.
- Check breaking changes, migrations, security impact, issue references, and required repository trailers.
Format
- Subject:
<type>(<scope>): <imperative summary>; omit scope when unhelpful. - Prefer 50 characters or fewer; never exceed 72.
- Use the repository's existing capitalization and type conventions.
- Use an imperative verb and no trailing period.
- Add a wrapped body only for rationale, breaking changes, migrations, security implications, reverts, or issue context.
- Keep
BREAKING CHANGE:and required trailers exact.
Do not add AI attribution unless the user's or repository's rule explicitly requires it. Do not remove a required attribution trailer.
Output
Return one paste-ready code block. If evidence is insufficient, state the missing fact before the draft rather than inventing it.