Generate Conventional Commit messages for staged changes with type, scope, and subject.
npx skills add https://github.com/huangzida/skills --skill caveman-commit-huangzida
Please help me install this Agent Skill. Skill: caveman-commit Source: https://github.com/huangzida/skills/tree/main/caveman-commit Command: npx skills add https://github.com/huangzida/skills --skill caveman-commit-huangzida
Conventional commits are the standard for messaging changes in a codebase, but teams often struggle to keep messages terse while preserving intent and rationale. This skill provides a deterministic template that trims noise while ensuring the subject, scope, and optional body convey essential context.
Provide a concise Conventional Commit message for the current staged changes.
High-intent search queries and answers about installing and using this skill.
To generate a conventional commit message, this skill analyzes your staged git changes and outputs a concise subject in the form <type>(<scope>): <imperative summary> with an optional body when needed, automatically trimming fluff while preserving essential context.
The conventional commit subject limit is 50 characters. Keeping the subject within this limit ensures diffs remain readable, while further rationale or context is moved into an optional body paragraph only when strictly necessary.
To keep git commit messages concise without losing intent, use a deterministic template that enforces type, optional scope, and an imperative summary. This trims noise while ensuring the subject and optional body convey essential context for history readability.
Yes, you can apply AI to write conventional commits for staged code changes on-demand via natural-language prompts. The generation strictly follows conventional commit syntax, omitting any mention of the tool itself or AI in the final message.
No, you do not need to manually specify the scope and type. The skill analyzes your staged changes and automatically determines the appropriate type and optional scope, formatting the message into the required <type>(<scope>): <imperative summary> structure.
You should include a body in a conventional commit message only when additional rationale is necessary. The default output focuses on a concise subject under 50 characters, adding the body paragraph solely to convey essential context that cannot fit in the summary.
im9Generate a conventional commit message and commit staged files.
mhattingpeteStage, commit, and push code changes with conventional commit messages.
GLaDO8Generates concise Git commit messages and commits staged or unstaged changes.
TruvetaPublicGenerate conventional commit messages by analyzing git diffs.
