From skillz
Generate a conventional-commit message from staged changes. Use when asked to write a commit message or describe staged changes.
How this skill is triggered — by the user, by Claude, or both
Slash command
/skillz:commit-messageThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Generate a commit message for the currently staged changes.
Generate a commit message for the currently staged changes.
git diff --cached to see staged changesgit diff --cached --stat for a file-level summarygit diff for unstaged changes and let the user know they need to stage firstUse conventional commits:
<type>(<scope>): <short summary>
<body — what changed and why>
Types: feat, fix, refactor, docs, test, chore, perf, ci, build, style Scope: The primary module, component, or area affected Summary: Imperative mood, lowercase, no period, under 72 chars Body: Explain the motivation and what changed. Focus on why, not what (the diff shows the what).
code-review — review code before committingGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.
npx claudepluginhub zmackie/skillz --plugin skillz