commitkit

Create Conventional Commits messages from the git diff and push grouped commits to origin.

1|Updated Jul 12, 2026
One-click install
npx skills add https://github.com/mimukit/skills --skill commitkit-mimukit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commitkit
Source: https://github.com/mimukit/skills/tree/main/skills/commitkit
Command: npx skills add https://github.com/mimukit/skills --skill commitkit-mimukit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing commit messages by hand at the end of a long coding session is tedious and often produces vague, catch-all commits. This Skill reads the actual diff, groups the work into logical units, and writes well-formed Conventional Commits messages for each group, then commits and pushes them. ## Core Features & Use Cases - Diff-grounded messages: Infers the commit type and mandatory scope from what the diff actually does, producing imperative, lowercase subjects with a required body explaining why. - Multi-commit grouping: Splits a session's changes into one commit per feature group or logical unit, staging and committing each group in a single chained Bash call. - Draft mode: When a git tool like lazygit inlines the staged diff, emits exactly one raw commit message with no extra output, ready to drop into a commit panel. - Push and hand-off: Pushes fast-forward commits to origin by default, reports a summary table of commits, and names the next move (open a PR, reply to review, or keep building). - Use Case: After finishing a feature branch with changes across auth, tests, and CI config, say "commit my changes" and receive three scoped commits, pushed, with a summary table and the PR link. ## Quick Start Ask the agent to commit your current changes by saying "commit this" or "/commitkit" and it will group, message, commit, and push the work.

Frequently Asked Questions about commitkit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a Conventional Commits message from my git diff?

Run the skill with a request like "commit this" and it reads git status and the diff, picks a type (feat, fix, docs, refactor, etc.) from what the change does, assigns a mandatory scope, and writes an imperative lowercase subject with a required body of reason bullets.

How do I split one coding session into multiple git commits?

The skill groups changes by logical unit of work, not by file type, keeping a feature with its tests and docs. It stages and commits each group in one chained Bash call, ordering groups so dependencies land first.

Can I generate a commit message without committing, for lazygit or another tool?

Yes. Draft mode activates when the caller inlines the staged diff in <staged-diff> tags with no tools available. The skill outputs exactly one raw commit message with no preamble or formatting, ready for a commit panel.

Does the skill push commits automatically?

It pushes by default when the push is a plain fast-forward to origin and the branch tracks origin or has no upstream. It holds the push and asks when the remote rejects it, no origin exists, or the user said not to push.

Will it ever amend, rebase, or force-push my commits?

No. The skill never runs git commit --amend, rebase, reset, or any history-rewriting command unless the user explicitly asks, and it never uses --force after a rejected push.