Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From git-toolkit
Generates conventional commit messages based on staged changes. Use when the user wants to commit with a well-formatted message following the Conventional Commits specification.
How this skill is triggered — by the user, by Claude, or both
Slash command
/git-toolkit:conventional-commitThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Analyze the current staged changes (`git diff --cached`) and generate a commit message following the Conventional Commits specification:
Analyze the current staged changes (git diff --cached) and generate a commit message following the Conventional Commits specification:
<type>[optional scope]: <description>
[optional body]
[optional footer(s)]
Present the suggested message and ask for confirmation before committing.
npx claudepluginhub walis85300/marketplace --plugin git-toolkitGenerates conventional commit messages from staged changes by analyzing git diffs and determining type, scope, and breaking changes.
Generates Conventional Commits messages for staged git changes and commits them. Follows v1.0.0 spec with types like feat, fix, refactor. Use for standardized commits or /commit invocation.
Generates clear, conventional commit messages from git diffs. Useful when writing commit messages, reviewing staged changes, or preparing commits.