From k
Stage intentional changes and create a clean git commit with deliberate staging, required quality checks, and a well-formed message.
How this skill is triggered — by the user, by Claude, or both
Slash command
/k:commitThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
1. Read `CLAUDE.md` for project-specific quality commands, then run every applicable check before staging.
CLAUDE.md for project-specific quality commands, then run every applicable check before staging.
git status and git diff.
git add ..git diff --staged and confirm the staged set is coherent and intentional.feat: or fix: prefixes.Add email validation to user registration
Replace session store with Redis
Cookie-based sessions hit the 4KB limit for users with large
permission sets. Redis removes the size cap and reduces
per-request payload.
Added email validationAdds email validationfeat: add email validationgit commit only when the change is a clean logical unit that can stand on its own.npx claudepluginhub kkestell/skills --plugin kGuides systematic git commits: checks staging status, reviews diffs, splits changes into atomic commits, formats conventional messages. Use before PRs or when committing code.
Git commit workflow pipeline: atomic unit identification, commit ordering, quality gates, message validation, and post-commit verification. Invoke whenever task involves any interaction with git commits — committing changes, staging work, splitting diffs into atomic units, or preparing work for version control.
Stages intended git changes avoiding secrets and creates clear Conventional Commits like feat(scope): subject. Useful for clean, semantic commit history.