
Commit
- Updated April 7, 2026
- clemux/claude-code-plugins
commit creates smart conventional commits by automatically analyzing changes and splitting unrelated work into separate commits. Developers use it to keep a clean, conventional git history without hand-grouping diffs. It is a lightweight git workflow helper.
Key points
- Conventional commits
- Automatic change analysis
- Splits unrelated changes
Commit by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
/plugin marketplace add clemux/claude-code-plugins/plugin install commit@clemux-claude-code-pluginsAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Last updated | April 7, 2026 |
|---|---|
| Repository | clemux/claude-code-plugins ↗ |
What it does
Creates smart conventional commits with automatic change analysis and splitting of unrelated changes.
README.md
commit
A Claude Code plugin for smart conventional commits with automatic change analysis and splitting via the /commit command.
Installation
From the marketplace
/plugin marketplace add clemux/claude-code-plugins
/plugin install commit@clemux-claude-code-plugins
From a local clone
claude --plugin-dir ~/dev/claude-code-plugins/commit
Usage
/commit # Analyze changes, propose commits, execute after confirmation
/commit push # Same, then push to remote
/commit auto # Skip confirmation, auto-execute commits
What it does
- Analyzes staged and unstaged changes (git status, diff, log)
- Groups changes into logical commits using intent-based splitting heuristics
- Proposes a commit plan with conventional commit messages
- Presents the plan for user confirmation (unless
autois used) - Dispatches haiku subagents to execute git add + commit
- Handles pre-commit hook failures (fixes issues, creates new commits)
- Pushes if requested
How it works
Unlike test-runner (thin skill, heavy subagent), commit inverts the pattern:
- The
/commitskill is heavy: Opus does all analysis, splitting heuristics, commit planning, and hook failure handling - The
commitsubagent is thin: Haiku just executes git commands and reports structured results (OK/HOOK_FAILED/ERROR)
The custom commit subagent type enables proper attribution in subagent-metrics logs.
Safety rules
- Never force-push, amend, or skip hooks
- Never push unless explicitly requested
- Always uses specific file paths (never
git add .) - Always uses conventional commit format
- Always confirms with user before executing (unless
auto)
Files
| File | Purpose |
|---|---|
agents/commit.md |
Custom haiku subagent (Bash only) for git execution |
skills/commit/SKILL.md |
/commit slash command with multi-phase workflow |