Generates git commit messages from staged diffs with strict formatting rules.
npx skills add https://github.com/kveperedo/website --skill commit-message-kveperedo
Please help me install this Agent Skill. Skill: commit-message Source: https://github.com/kveperedo/website/tree/main/.agents/skills/commit-message Command: npx skills add https://github.com/kveperedo/website --skill commit-message-kveperedo
git diff --staged, analyzes the changes, and writes an imperative subject line plus a dash-list body. - Strict format enforcement: Subject capped at 50 characters, body lines hard-wrapped at 72 characters, dash-prefixed body items only, validated before display. - Atomic commit splitting: Detects logically distinct changes (bug fix plus feature, refactor plus behavior change) and proposes a sequenced multi-commit plan with per-commit confirmation. - Use Case: You staged a diff containing a login bug fix, a new dark-mode toggle, and dependency updates. The Skill proposes three separate commits, stages each group, shows each message for approval, and commits them in dependency-first order. ## Quick Start Ask the assistant to generate a commit message for your staged changes and confirm the proposed message before it commits.High-intent search queries and answers about installing and using this skill.
Stage your changes with git add, then ask for a commit message. The Skill runs git diff --staged, analyzes the diff, and outputs a subject line under 50 characters plus a dash-prefixed body wrapped at 72 characters for your approval.
The Skill detects logically distinct changes such as a bug fix mixed with a feature, proposes a split plan, unstages everything, then stages and commits each group sequentially. Commits are ordered dependencies first, then refactors, features, and tests.
The format requires an imperative-mood subject of at most 50 characters with no trailing period, one blank line, then a body of dash-prefixed items each under 72 characters and capped at six items. Conventional-commits prefixes are omitted unless the project already uses them.
No. The full commit message is always displayed in a fenced code block first, and the Skill asks for explicit Yes/No confirmation before running git commit. Rejected messages can be adjusted or skipped.
The Skill falls back to running git diff on unstaged changes and notes that it did so. It then generates the message from that diff instead of stopping.
darknightCommit staged Git changes after passing lint checks.
santychuycomAnalyze diffs, create atomic conventional commits, push, and open pull requests.
MolcajeteAIConfigure Husky and lint-staged pre-commit hooks for automated code quality checks.
punkfuncgamesStandardize git commit messages using the Conventional Commits format.