Caveman commit
Skill yigityildiz0/universal-ai-skill-library/skills/common/caveman-commit
531 searchable AI Agent Skills for Claude Code, OpenAI Codex, and OpenCode — EN/TR catalog, platform and risk notes, direct ZIPs, and curated bundles.
npx -y skills add yigityildiz0/universal-ai-skill-library --skill caveman-commitAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
3 things to look at
- 19 days oldThe repository was created 19 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Draft a terse Conventional Commit message while preserving intent, rationale, breaking-change details, and repository conventions. Use only when the user explicitly invokes $caveman-commit or specifically asks for a Caveman-style commit message. Do not trigger for generic commit or staging requests.
SKILL.md
1.5 KB, 246 tokens by cl100k_base, as published. Nobody here has run it
Caveman Commit
Draft the message only. Do not stage, commit, amend, push, or change files.
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.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.