commit · kklimuk — Claude Code skill: commits and installation
A Git commit skill for Claude Code organizes changes in the working tree. It activates when asked to save work or create a commit.
MIT ★ 251 updated 2026-11-12
npx skills add kklimuk/docx-cli --skill commit -a claude-codeWhat commit does
The skill checks the working tree, reviews the diff, and reads recent commit messages to follow the repository’s style. It groups files by intent, then presents the proposed commit count, messages, and file lists for confirmation.
For each approved commit, it stages named files individually and writes a message with a type such as feat or fix. It checks staged files for secrets and excludes .env files and credentials. Afterward, it displays recent commits. If a pre-commit hook fails, the skill investigates its configured commands and creates a new commit after the fix; it does not amend the previous one.
What it helps with
- group working-tree changes by intent
- prepare commit messages in a consistent format
- check staged files for secrets before committing
- make a separate commit after fixing a pre-commit failure
Example prompts for the agent
- Commit my current changes.
- Sort the working-tree changes into commits and show me the plan.
- Create a commit for the bug fix.
How to install commit
1Skills CLI (Vercel)
npx skills add kklimuk/docx-cli --skill commit -a claude-code2Manually: put the files in place
~/.claude/skills/commit/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/commit/
1Skills CLI (Vercel)
npx skills add kklimuk/docx-cli --skill commit -a codex2Manually: put the files in place
.agents/skills/commit/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add kklimuk/docx-cli --skill commit -a cursor2Manually: put the files in place
.cursor/skills/commit/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install kklimuk/docx-cli .claude/skills/commit2Manually: put the files in place
.github/skills/commit/SKILL.md1Skills CLI (Vercel)
npx skills add kklimuk/docx-cli --skill commit -a gemini-cli2Platform CLI
gemini skills install https://github.com/kklimuk/docx-cli --path .claude/skills/commitManually: put the files in place
.devin/skills/commit/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add kklimuk/docx-cli --skill commit -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about commit
How do I install commit in Claude Code?
Run npx skills add kklimuk/docx-cli --skill commit -a claude-code. The skill file is at ~/.claude/skills/commit/SKILL.md.
What does the commit skill do?
It reviews the working tree, proposes file groups and commit messages, then creates commits after confirmation. It also checks staged files for secrets and displays the Git log afterward.
What happens if a pre-commit hook fails?
The skill inspects the hook configuration and runs its commands separately to locate the failure. After fixing it, the skill creates a new commit rather than amending the previous one.
Source text
SKILL.md · MIT
--- name: commit description: "Create well-structured git commits from the current working tree. Use when the user says 'commit', 'save my work', 'let's commit this', 'make a commit', or any variation of wanting to commit code to git." metadata: internal: true --- # Commit Create clean, well-structured git commits that tell a coherent story. ## Process ### 1. Assess the Working Tree Run `git status` (never `-uall`) and `git diff` to understand what changed. Also run `git log --oneline -5` to match the repo's existing commit message style. If there are no changes, say so and stop. ### 2. Group Changes by Intent Look at the changed files and mentally group them: - **Feature**: new functionality (client + server + tests for the same feature = one commit) - **Fix**: bug fixes - **Refactor**: structural changes that don't change behavior - **Docs**: documentation-only changes (CLAUDE.md, README, comments) - **Test**: test-only additions or changes - **Chore**: config, dependencies, tooling Rules for grouping: - **Prefer fewer commits.** A feature that touches 15 files is still one commit if it's one logical change. - **Only split when intent is genuinely different.** "Add collaborative editing" is one commit even if it touches client, server, DB, and tests. But "add collaborative editing" + "fix unrelated CSS bug" should be two commits. - **For a first commit or large initial build, one commit is fine.** Don't artificially split an initial implementation. - **Docs updates that accompany code changes go in the same commit.** Only separate docs commits for docs-only changes. ### 3. Present the Plan Before committing, show the user: - How many commits you plan to make - For each commit: the message and which files are included - Ask for confirmation ### 4. Create the Commits For each commit: 1. Stage the specific files with `git add <file1> <file2> ...` (never `git add -A` or `git add .`) 2. Commit with a message using this format: ``` <type>: <concise description> <optional body — explain WHY, not WHAT. The diff shows what.> Co-Authored-By: Claude <[email protected]> ``` Types: `feat`, `fix`, `refactor`, `docs`, `test`, `chore` Message guidelines: - Subject line under 72 characters - Use imperative mood ("add", not "added" or "adds") - The subject should complete the sentence "This commit will..." - Body is optional — use it for non-obvious context (e.g., "the old approach caused X" or "this unblocks Y") - Always include the Co-Authored-By trailer ### 5. Verify After all commits, run `git log --oneline -10` to show the result. ## Safety Rules - **Never commit `.env`, credentials, or secrets.** Check staged files for these patterns and warn. - **Never use `git add -A` or `git add .`** — always stage specific files. - **Never amend a commit** unless the user explicitly asks. - **Never force push.** - **Never skip hooks** (`--no-verify`). - **If a pre-commit hook fails**, fix the issue and create a NEW commit (don't amend). To diagnose, read the pre-commit hook (`.husky/pre-commit` or `.pre-commit-config.yaml`) to see what it runs, then run each command individually to find the failure. ## What NOT To Do - Don't write commit messages that describe every file changed. The diff does that. - Don't split a single feature across 5 commits just because it touches 5 directories. - Don't use vague messages like "update code" or "fix stuff". - Don't commit generated files (`db/schema.ts`, `dist/`, `node_modules/`, `__pycache__/`).
© kklimuk · MIT · kklimuk/docx-cli
Similar skills
All skills for Git and GitHub →commit by other authors comes first.