kick-ass-commit
Create world class, high quality commit messages that clarify what changed and why. Use when preparing to commit or when the user requests outstanding commit messages.
- License 许可
- Apache-2.0
- 最近更新
- 2026-10-30
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- kick-ass-commit
- metadata
- { "author": "andrebot", "version": "1.1" }
- description
- Create world class, high quality commit messages that clarify what changed and why. Use when preparing to commit or when the user requests outstanding commit messages.
03 SKILL.md 正文
Kick-Ass Commit
Overview
Create world class, high quality commit messages that make it easy for people and coding agents to understand what happened.
Steps
- Collect the set of modified and untracked files (staged and unstaged).
- Inspect diffs for all files that will be committed.
- Check for documentation updates, including
README,CHANGELOG, or similar files. - Determine an appropriate scope and a concise summary of the changes.
- Draft a commit message using the template and include clear, factual bullet points.
- When executing
git commit, keep shell quoting safe: do not wrap file paths or snippets in backticks inside-mvalues because backticks trigger command substitution. - Immediately validate the final commit message with
git log -1 --format=%Bbefore any push. - If the message is malformed and the commit is not pushed yet, fix it with a new
git commit --amend -m "..." -m "...", then re-validate. - If the malformed commit was already pushed, do not rewrite history unless the user explicitly requests it; otherwise create a follow-up commit that corrects the record.
Inputs
- Repository state (status, diff, staged files).
- Optional scope hint from the user.
Outputs
- A commit message in the requested template.
- A short note if documentation changes are detected or missing.
- A validated final message check before push (
git log -1 --format=%B).
Edge cases
- If no changes are present, do not draft a commit; report that there is nothing to commit.
- If documentation changes are expected but missing, call it out and suggest adding them.
- If the scope is unclear, infer it from the dominant change area.
- If message text needs inline code formatting, keep markdown backticks in design notes only; do not include them in shell-executed
git commit -marguments.
Commit template
[scope]: Brief description of changes
- Detailed bullet point about what changed
- Second detail point
- Nth detail point (as many as needed)
- N + 1th detail point
- etc.
Example prompts
- "Craft a world class commit message for these changes"
- "Create a kick-ass commit message for this repo"
04 同仓库更多 Skills
Beta Skill
Instruction-only fixture skill.
Alpha Skill
First fixture skill with a runnable demo.
Deck One
A small deck template fixture.
youtube-clipper
YouTube clip generation and editing with automated workflows — pull source video, slice highlights, add captions, and export.
writing-guidelines
Review docs/prose for Writing Guidelines compliance. Use when asked to "review my docs", "check writing style", "audit prose", "review docs voice and tone", or "check this page against the writing handbook".
wpds
WordPress Design System. Apply WordPress's official design tokens, typography, and component patterns to themes and sites.