From dmv
Commit changes with smart messages. Supports full and partial commits. Use whenever committing changes or handling pre-commit hook failures.
How this skill is triggered — by the user, by Claude, or both
Slash command
/dmv:commitThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
1. **Interpret arguments** — `$ARGUMENTS` could be any of:
Interpret arguments — $ARGUMENTS could be any of:
Use judgment based on context. Don't ask unless unclear — infer if possible.
Analyze repository state:
git status — see all changesgit diff and git diff --staged — see what's changedStage files:
git add .)Generate or use commit message following these requirements:
fix:, feat:, refactor:, etc.)Good: prevent race condition in session cleanup, rate limiting middleware
Bad: fix: correct bug, updates, add new feature ✨, fix bug.
Commit:
git commit -m "message"
Handle pre-commit hook failures:
Pre-commit hooks (formatters/linters) sometimes auto-modify files during commit, causing it to fail because git won't commit when the working directory changes mid-process.
git add . then git commit --amend --no-editgit log -1 --format='%an <%ae>' — never amend someone else's commitVerify: git status and git log -1 --oneline
npx claudepluginhub racurry/neat-little-package --plugin dmvCreates semantic git commits with conventional commit format, stages changes, and pushes to remote. Handles pre-commit hooks and writes meaningful commit messages.
Creates local Git commits with conventional messages and GitHub issue references. Handles staging, pre-commit hooks, and automatic issue detection from changes.
Creates git commits matching repository style. Stages files explicitly and writes concise commit messages in imperative mood.