caveman-commit · Skill Details

Mechanism

When It Triggers · How It Works · What It Produces

Breaks down how the skill works and what it produces, so you can quickly judge whether it fits your scenario and value.

Trigger

User says "write a commit", "commit message", "generate commit", "/commit", or invokes /caveman-commit.
Auto-triggers when user stages changes.

Mechanism

Subject format: <type>(<scope>): <imperative summary>, scope optional. Types: feat/fix/refactor/perf/docs/test/chore/build/ci/style/revert.
Subject ≤50 chars (hard cap 72), no trailing period. Imperative mood (add/fix/remove, not added/adds/adding).
Body only when needed: non-obvious why, breaking changes, migration notes, linked issues.
Strictly excludes: "This commit does X", I, we, now, currently, AI attribution.
Output as Markdown code block for manual paste into git commit.

Result

Minimal commit message conforming to Conventional Commits format.
Body contains only necessary "why" information, not repeating what the diff already shows.
Auto-supplements detailed body for breaking changes, security fixes, etc.

Use Cases

Two Typical Use Cases

Scenario 01

Quickly generating standardized commit messages

After completing code changes, the developer types `/caveman-commit` or says "write a commit", "commit message", "generate commit". The agent auto-reads the staged diff and generates a Conventional Commits message: `feat(api): add GET /users/:id/profile`. Body is added only when explaining "why" (non-obvious reasons, breaking changes, etc.). The message is output as a code block ready to copy-paste.

Scenario 02

Detailed changelogs for breaking changes and security fixes

For breaking API changes, security fixes, data migrations, or revert commits that require additional context, caveman-commit's Auto-Clarity mechanism ensures the generated message includes a full body. For example, breaking changes get `BREAKING CHANGE:` with migration path and timeline, and security fixes include CVE references. This information is critical for future debugging and maintenance and is never over-compressed.

Skill Relationships

Which Skills I Use · Which Skills Use Me

Dependency relationships read as "the upper tier points to the lower tier." The current Skill sits in the middle tier — above are Skills that depend on it, below are Skills it depends on.

Tier 1 · These Skills Use Me

caveman-helpCLI Manual

Tier 2 · Current Skill

caveman-commitWorkflow

Tier 3 · I Use These Skills

No explicit dependency on other Skills

Full Relationship Graph

Browse this skill's relationships within its skillset. Click a node to switch the side panel; use the search box to jump to any skill.

Skill File

SKILL.md

Open in GitHub ↗

SKILL.mdLoading from GitHub…

Skill Composition

Open in GitHub ↗

SKILL.md50.0%
other50.0%

▸skills/caveman-commit/
▸caveman-commit
- ·README.md
- ·SKILL.md

Per the Agent Skills spec, SKILL.md is the only required file. The colored bars classify the rest into the three spec-aligned optional directories (scripts / references / assets) and an 'other' bucket. The full directory tree is below.

Related in Skillset

You May Also Need These Skills

cavecrew

The cavecrew skill provides a delegation decision guide for three caveman-style subagent presets: `cavecrew-investigator` (locate code), `cavecrew-builder` (surgical 1-2 file edits), and `cavecrew-reviewer` (diff review). Subagent output is caveman-compressed, returning tool results ~60% smaller into main context than standard subagents. Key output: ~60% context token savings per delegation, letting the main thread accomplish more before context exhaustion.

Workflow

caveman

The caveman skill is the core of the Caveman skillset. It saves ~65% output tokens by making the AI coding agent reply in ultra-terse "caveman speak". Supports 6 intensity levels (lite/full/ultra/wenyan), strips filler/pleasantries/hedging while preserving code, technical terms, and error messages verbatim. Key output: dramatically reduced output token consumption per session, faster code reading, lower API costs.

Workflow

caveman-compress

The caveman-compress skill compresses natural language memory files (CLAUDE.md, todos, preferences) into caveman format, saving ~46% input tokens on every subsequent session. It uses a Python script (`scripts/__main__.py`) for automated compression, preserving all technical content, code, URLs, and structure. The compressed version overwrites the original, with a human-readable backup saved as `FILE.original.md`. Key output: compress once, save tokens every session forever.

Workflow

caveman-help

The caveman-help skill provides a quick-reference card for all caveman modes, skills, and commands. It is one-shot display only — it does not change any mode or persist anything. When triggered by `/caveman-help`, "caveman help", or "what caveman commands", the agent outputs a caveman-style reference table covering all modes (lite/full/ultra/wenyan), skills (commit/review/compress/help), and configuration tips. Helps users quickly grasp the full caveman ecosystem.

CLI Manual