How this skill is triggered — by the user, by Claude, or both
Slash command
/sunny:commitThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
<!--
Analyze the current git changes and generate a conventional commit message, then ask for confirmation before committing.
git status to see what files are changed, staged, or untracked.git diff --staged to see staged changes. If nothing is staged, run git diff to see unstaged changes and inform the user.feat — new feature or capabilityfix — bug fixrefactor — restructuring without behavior changedocs — documentation onlychore — tooling, config, dependenciestest — adding or updating testsstyle — formatting, whitespaceperf — performance improvement<type>(<optional scope>): <short imperative summary>
<optional body — what and why, not how>
git commit -m "<message>" (use heredoc for multi-line).git add -A or git add . — only commit what is already staged.git add, inform them and stop.npx claudepluginhub kolatts/claude-marketplace --plugin sunnyDrafts Conventional Commits messages for staged git changes. Proposes a type-scoped subject line, waits for user approval, then commits.
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.
Stages intended git changes avoiding secrets and creates clear Conventional Commits like feat(scope): subject. Useful for clean, semantic commit history.