# Caveman Commit

> Manual Caveman-style Conventional Commit message generator that preserves intent, rationale, breaking-change details, and repository conventions. Use only when explicitly invoked as $caveman-commit, /caveman-commit, 'Caveman commit', or an equally unambiguous request for a Caveman-style commit message. Never activate for generic commit, staging, or commit-message requests. Turkish triggers: Caveman commit, mağara modu commit mesajı.

- Skill: `yigityildiz0/caveman-commit` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add yigityildiz0/caveman-commit`
- Raw SKILL.md: https://api.skillmd.com/api/skills/yigityildiz0/caveman-commit/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- License: MIT
- Author: yigityildiz0 (https://skillmd.com/u/yigityildiz0)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/yigityildiz0/caveman-commit

---


# Caveman Commit

Draft the message only. Do not stage, commit, amend, push, or change files.

Safety-adapted from [JuliusBrussee/caveman](https://github.com/JuliusBrussee/caveman), MIT licensed. Preserve the included `LICENSE` when redistributing.

## Workflow

1. Inspect the relevant diff and recent commit convention when available.
2. Identify the change type, scope, user-visible effect, and non-obvious why.
3. Draft the shortest message that preserves those facts.
4. 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.