commitkit

# commitkit Turn the current changes into one or more clean commits with [Conventional Commits](https://www.conventionalcommits.org) messages inferred from the diff itself — not from a guess. The message describes what actually changed, in the imperative mood, with a correct type and scope. In a coding session the default is **multiple commits**, one per feature group or logically related change — not a single catch-all commit. ## When this fires The user asks to commit ("commit this", "make a commit", "/commitkit", "commit my changes"). If they only want a *message drafted* (not committed), do everything except the final `git commit`. This skill is built for AI coding sessions where the user hands off with a bare "commit". In that mode you are expected to work autonomously: stage the right files yourself, group the work into as many commits as it deserves, commit them, and report back a table of what you created — without stopping to ask at each step. ## Procedure ### 1. Read the state Run these together and read the output before deciding anything: ```sh git status --short git diff --staged git diff # unstaged, for context ``` - When the user has **delegated committing** (the typical coding-session "commit" / "commit my changes"), you are free to stage the files you need yourself — `git add` the paths for each logical group as you commit it. You don't have to ask first; grouping and staging is your job here. - Only pause to ask when intent is genuinely am...