Skip to content
Skills Library
Programming · Writing

cavemenko-commit

/cavemenko-commit

Generate short commit messages in Conventional Commits format. Use when user asks to generate commit, describe changes for git, or calls /cavemenko-commit.

Repository
cavemenko ↗
Licence
MIT
Last repository change
12.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 12.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Generate short commit messages in Conventional Commits format. Use when user asks to generate commit, describe changes for git, or calls /cavemenko-commit.

Original author description

Generate short commit messages in Conventional Commits format. Use when user asks to generate commit, describe changes for git, or calls /cavemenko-commit.

How it works

  1. Format
  2. Rules
  3. Examples
  4. Process
Original SKILL.md headings · 51 lines, 178 words
SKILL.md preview
---
name: cavemenko-commit
description: >
  Generate short commit messages in Conventional Commits format.
  Use when user asks to generate commit, describe changes for git,
  or calls /cavemenko-commit.
---

Generate short commit msg for current staged changes.

## Format

Conventional Commits. Structure: `<type>(<scope>): <description>`

Types: `feat`, `fix`, `docs`, `style`, `refactor`, `perf`, `test`, `chore`, `build`, `ci`

## Rules

- Subject: ≤50 chars, imperative, lowercase after type
- No period at end of subject
- Body: only when "why" is not obvious from subject
- Explain **why**, not **what** — `git diff` already shows what
- Empty line between subject and body
- Body: wrap at 72 chars

## Examples

Good:
```
fix(auth): check token expiry with strict inequality

Previous check used `<=` which accepted tokens at exact expiry time.
Clock skew between services caused intermittent 401s.
```

Good (self-sufficient subject):
```
docs: fix typo in README install instructions
```

Bad:
```
Updated some files.
```

Bad (repeating what diff shows):
```
feat: add new function called validateInput to utils.js
```

## Process

1. Read `git diff --cached`
2. Determine type and scope
3. Write subject (≤50 chars, imperative)
4. Decide if body needed — only if "why" not obvious
5. Output ready message in one block, no explanations

Versions

The database has no other skills named cavemenko-commit.

Database snapshot: 13.11.2026 · package version a8d5e8e04edd (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100commit-message
    Generate conventional commit messages - use when creating commits, writing commit messages, or asking for git commit help
  • 100git-commit
    Generate conventional commit messages for Java projects. Use when user says "commit", "create commit", "commit changes", or after completing code changes that need to be committed.
  • 100cavemenko-review
    One-line code review comments. Use when user asks to review code, check changes, or calls /cavemenko-review.
  • 100commit-message
    Generate descriptive commit messages by analyzing git diffs. Use when the user asks for help writing commit messages, reviewing staged changes, or wants to commit with a well-formatted message following conventional commits format.
  • 100commit-helper
    Helps write Git commit messages following the Conventional Commits specification. Use this skill when the user asks to commit changes, write commit messages, format commits, or mentions git commits.
  • 84generate-commit-message
    Generate well-structured git commit messages. Use when user says "generate commit message", "write a commit", "what should my commit message be", "create commit message for these changes", or needs help crafting conventional commit messages.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.