New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Commit

by kklimuk in kklimuk/docx-cli

Create well-structured git commits from the current working tree.

MITAuto-check: notesDevelopment

Install Commit

skills CLI
$ npx skills add kklimuk/docx-cli --skill commit -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install kklimuk/docx-cli commit --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/kklimuk/docx-cli.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/commit .claude/skills/commit && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
commit
GitHub stars
216
Token cost
~877 tokens
SKILL.md length
454 words
Files
1
Skills in repo
4
Repo updated
First seen
Licence
MIT

At a glance

Create well-structured git commits from the current working tree.

  • Works in 5 steps: Assess the Working Tree → Group Changes by Intent → Present the Plan → …
  • The user says commit
  • SKILL.md covers Process, Safety Rules and What NOT To Do
  • Calls git

What it does

Commit is an agent skill from kklimuk/docx-cli. 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.

Its SKILL.md is about 880 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Commit messages. It works with Git. The repository describes itself as: CLI for AI agents (Claude, Codex) to read, edit, and comment on .docx files with full format fidelity. The licence is MIT.

When your agent uses it

  • The user says commit
  • Lets commit this
  • Any variation of wanting to commit code to git

Example prompts

  • “commit”
  • “save my work”
  • “s commit this”
  • “/commit”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Assess the Working Tree
  2. Group Changes by Intent
  3. Present the Plan
  4. Create the Commits
  5. Verify

What it can do on your machine

Read from SKILL.md and the folder at commit 74672e4. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Commit loads about 877 tokens when it runs. Until then it costs about 53 tokens; SKILL.md has 454 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~53
When it runs · the whole SKILL.md, loaded when a task matches
~877

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:73
    - **Never commit `.env`, credentials, or secrets.** Check staged files for these patterns and warn.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from kklimuk/docx-cli at commit 74672e4, republished under its MIT licence (© kklimuk). 454 words, ~877 tokens.

Download SKILL.mdSave it as .claude/skills/commit/SKILL.md (or your agent's skills folder).
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 <noreply@anthropic.com>

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
Show full SKILL.md (145 more words)Show less
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. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/commit of kklimuk/docx-cli.

Open the folder on GitHubat commit 74672e4

Compare with similar skills

Commit next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Commit compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Commit this skillkklimuk/docx-cli216—~877Automated safety check: NotesMIT
React Router Release Notes Prepremix-run/react-router57k—~1.1kAutomated safety check: PassMIT
ToolJet Multi-Repo CommitToolJet/ToolJet41k—~1.3kAutomated safety check: PassAGPL-3.0
Git Workflow and Versioningaddyosmani/agent-skills103k2 repos~3.5kAutomated safety check: NotesMIT
React Router Pull Request Creatorremix-run/react-router57k—~2.5kAutomated safety check: PassMIT
Verdaccio Pull Request Workflowverdaccio/verdaccio18k—~1.9kAutomated safety check: PassMIT

Similar skills

  • React Router Release Notes Prep

    remix-run/react-router

    Polishes pending React Router change files before the versioning scripts run, and decides whether a long-form What's Changed section is warranted.

    57k GitHub stars~1.1k tokensUpdated 2 days ago
    DevelopmentAuto-check passed

  • ToolJet Multi-Repo Commit

    ToolJet/ToolJet

    Commits changes across ToolJet's root repo and its server/ee and frontend/ee submodules, writing messages from the diffs and updating submodule pointers in order.

    41k GitHub stars~1.3k tokensUpdated today
    DevelopmentAuto-check passed

  • Git Workflow and Versioning

    addyosmani/agent-skills

    Sets git habits for every change: short-lived branches, atomic commits with descriptive messages, clean pull requests, plus versioning, tagging and changelogs for releases.

    103k GitHub starsUsed in 2 repos~3.5k tokens
    DevelopmentAuto-check: notes

  • React Router Pull Request Creator

    remix-run/react-router

    Packages finished React Router work into a draft pull request: branch, commit, push, a written PR body and the right GitHub labels.

    57k GitHub stars~2.5k tokensUpdated 2 days ago
    DevelopmentAuto-check passed

  • Verdaccio Pull Request Workflow

    verdaccio/verdaccio

    Takes a change through a verdaccio pull request: branch, local checks, changeset, title and body, labels, CI and review rounds, and ports to other release lines.

    18k GitHub stars~1.9k tokensUpdated 2 days ago
    DevelopmentAuto-check passed

  • Saleor Commit Workflow

    saleor/saleor

    Commits changes in the Saleor codebase and works through pre-commit hook failures from ruff, mypy, the GraphQL schema check and the migrations check.

    23k GitHub stars~575 tokensUpdated yesterday
    DevelopmentAuto-check passed

More from kklimuk/docx-cli

  • Weak Agent Test

    kklimuk/docx-cli

    Run the weak-agent adversarial test harness against docx-cli.

    216 GitHub stars~6.1k tokensUpdated 13 days ago
    Auto-check: notes

  • DOCX CLI

    kklimuk/docx-cli

    Read, edit, redline, comment on, and create Microsoft Word .docx files.

    216 GitHub stars~1.9k tokensUpdated 13 days ago
    Auto-check: warnings

  • Security Review

    kklimuk/docx-cli

    Review code for security vulnerabilities. An agent skill from kklimuk/docx-cli.

    216 GitHub stars~1.7k tokensUpdated 13 days ago
    Auto-check passed

Works with

Categories

Questions about Commit

What does Commit do?

Create well-structured git commits from the current working tree. Commit is an agent skill from kklimuk/docx-cli. Create well-structured git commits from the current working tree.

When should I use Commit?

Commit fits situations like: the user says commit; lets commit this; any variation of wanting to commit code to git.

How do I install Commit in Claude Code?

Run `npx skills add kklimuk/docx-cli --skill commit -a claude-code`. Or copy the skill folder (.claude/skills/commit in kklimuk/docx-cli) into .claude/skills/commit in your project. Claude Code loads it when a task matches its description.

How do I install Commit in Codex?

Run `npx skills add kklimuk/docx-cli --skill commit -a codex`. Or copy the skill folder (.claude/skills/commit in kklimuk/docx-cli) into .agents/skills/commit in your project. Codex loads it when a task matches its description.

Can I use Commit in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add kklimuk/docx-cli --skill commit -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/commit, .gemini/skills/commit, .github/skills/commit and .opencode/skills/commit in your project.

What does Commit need to run?

Going by SKILL.md and its folder, Commit needs the command-line tools its instructions call (git).

Does Commit access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Commit safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Commit use?

Commit is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Commit use?

About 877 tokens (SKILL.md is roughly 3.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Commit?

Skills that share tags, products or a category with Commit: React Router Release Notes Prep (remix-run/react-router, 57k stars), ToolJet Multi-Repo Commit (ToolJet/ToolJet, 41k stars), Git Workflow and Versioning (addyosmani/agent-skills, 103k stars) and React Router Pull Request Creator (remix-run/react-router, 57k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Commit?

kklimuk (a GitHub user) maintains it in kklimuk/docx-cli, which has 216 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on September 25, 2026.

Source: kklimuk/docx-cli on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.