caveman-commit

Generates concise Conventional Commits messages with 50-character subject lines.

Updated May 17, 2026
One-click install
npx skills add https://github.com/galeep/plugin-place --skill caveman-commit-galeep
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: caveman-commit
Source: https://github.com/galeep/plugin-place/tree/main/plugins/caveman/skills/caveman-commit
Command: npx skills add https://github.com/galeep/plugin-place --skill caveman-commit-galeep

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of creating clear, concise commit messages in the Conventional Commits format, making it easier to understand and maintain code history.

Core Features & Use Cases

  • Conventional Commit Format: Ensures commit messages adhere to a standard format for better readability and consistency.
  • Subject Line Constraints: Limits subject line length to 50 characters for brevity and clarity.
  • Imperative Mood: Uses imperative mood for subject lines to convey actions directly.
  • Body for Context: Provides a body for commits when necessary context is needed, such as for breaking changes or security fixes.

Quick Start

/caveman-commit

Frequently Asked Questions about caveman-commit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate conventional commit messages automatically?

You can generate conventional commit messages automatically by using this Skill, which enforces standard formatting, limits subject lines to 50 characters, and applies imperative mood for clear code history.

What is the conventional commits format for code history?

The conventional commits format structures commit messages with a concise subject line in imperative mood and an optional body, improving code review and maintainability for version control.

How do I write a commit message in imperative mood?

To write a commit message in imperative mood, frame the subject line as a direct command, such as 'fix' or 'add', which this Skill enforces automatically alongside a 50-character length limit.

Do I need external dependencies to enforce conventional commit rules?

You do not need external dependencies to enforce conventional commit rules, as this Skill operates independently to generate concise, standard-formatted commit messages for version control.

When do I need a body section in conventional commits?

You need a body section in conventional commits when necessary context is required, such as for documenting breaking changes or security fixes, which this Skill provides alongside the constrained subject line.