This skill helps Claude Code write commits that actually tell the story of the change.
It looks at what is staged and unstaged to understand what changed.
In practice it detects the commit type and scope from the diff and builds a message in the conventional commits format.
The message focuses on why the change was made, not just on listing the files that moved.
When to use
- Before each commit, to generate a clear message.
- When you want to keep a semantic, standardized history.
- To avoid generic messages like “fix” or “update”.
How to use
With your changes ready, ask “create a smart commit” or pass the type, like “commit-smart fix”.