skill CX Codex

commit · seifbenayed — Claude Code skill: well-formed git commits

Q: How do I install commit in Claude Code?

Run `npx skills add SeifBenayed/cloclo --skill commit -a claude-code`. The skill lands at `~/.claude/skills/commit/SKILL.md`.

Q: What does the commit skill do?

It runs `git status` and `git diff --cached`, suggests what to stage when the index is empty, then creates a commit with a conventional-commits message. The subject line stays under 72 characters.

Reads your staged changes and writes a conventional-commits message for them. Handy when the code is done but the wording is not.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓

npx skills add SeifBenayed/cloclo --skill commit -a claude-code

Open on GitHub

What commit does

The skill walks a fixed sequence. It starts with git status, then inspects git diff --cached line by line. Nothing staged? It falls back to git diff and points out which files look worth adding. A quick git log --oneline -5 follows, so the message matches the conventions already used in that repo.

Messages follow conventional commits: feat:, fix:, refactor:, docs:, test:, chore:. The subject stays under 72 characters, and a non-trivial change gets a body paragraph. The wording explains why the change exists, since the diff already shows what moved.

Tool access is limited to Bash, Read, Grep and Glob. No push happens unless you ask for one, and hooks are never skipped with --no-verify. That matters if your project runs pre-commit checks: they will still fire.

What it helps with

write a commit message in conventional commits format
see what is staged versus what is still sitting unstaged
match the commit style already used in the repo
record changes locally without pushing them
explain the reason behind a change instead of restating the diff

Example prompts for the agent

Commit these changes
Save changes as a commit
Commit this

How to install commit

1Skills CLI (Vercel)

npx skills add SeifBenayed/cloclo --skill commit -a claude-code

2Manually: put the files in place

~/.claude/skills/commit/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/commit/

1Skills CLI (Vercel)

npx skills add SeifBenayed/cloclo --skill commit -a codex

2Manually: put the files in place

.agents/skills/commit/SKILL.md

For all projects use ~/.agents/skills/

1Skills CLI (Vercel)

npx skills add SeifBenayed/cloclo --skill commit -a cursor

2Manually: put the files in place

.cursor/skills/commit/SKILL.md

Cursor also reads .agents/skills/ and .claude/skills/

1GitHub CLI

gh skill install SeifBenayed/cloclo commit

2Manually: put the files in place

.github/skills/commit/SKILL.md

1Skills CLI (Vercel)

npx skills add SeifBenayed/cloclo --skill commit -a gemini-cli

2Platform CLI

gemini skills install https://github.com/SeifBenayed/cloclo --path .claude/skills/commit

Manually: put the files in place

.devin/skills/commit/SKILL.md

The legacy .windsurf/skills/ path still works

Skills CLI (Vercel)

npx skills add SeifBenayed/cloclo --skill commit -a opencode

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 SeifBenayed/cloclo --skill commit -a claude-code. The skill lands at ~/.claude/skills/commit/SKILL.md.

What does the commit skill do?

It runs git status and git diff --cached, suggests what to stage when the index is empty, then creates a commit with a conventional-commits message. The subject line stays under 72 characters.

Does it push the commit for me?

No. Pushing only happens when you ask explicitly, and the skill does not pass --no-verify or skip hooks.

Source text

SKILL.md · MIT

---
name: commit
description: Create a git commit with a good message. Use when the user says "commit", "save changes", "commit this", or asks to create a commit after making code changes.
allowed-tools: Bash, Read, Grep, Glob
---

# Git Commit

Review all staged changes and create a well-crafted commit message.

## Steps

1. Run `git status` to see staged and unstaged changes
2. Run `git diff --cached` to review staged changes in detail
3. If nothing is staged, run `git diff` and suggest what to stage based on the changes
4. Run `git log --oneline -5` to see recent commit message style in the repo
5. Draft a concise commit message following conventional commits format:
   - `feat:` — new feature
   - `fix:` — bug fix
   - `refactor:` — code restructuring without behavior change
   - `docs:` — documentation changes
   - `test:` — adding or updating tests
   - `chore:` — build, tooling, config changes
6. Focus the message on **why** not **what** — the diff shows what changed
7. Keep the first line under 72 characters
8. Add a body paragraph if the change is non-trivial
9. Create the commit

Do NOT push unless explicitly asked. Do NOT use `--no-verify` or skip hooks.

$ARGUMENTS

Similar skills

All skills for Git and GitHub →

commit by other authors comes first.

commit getsentry A skill that drafts Sentry-style conventional commits with issue references and blocks direct commits to main. CX Codex +1 4,700installs commit NeoLabHQ Automates Git commits using conventional commit messages and matching emojis. It checks the active branch, runs pre-commit linters, and suggests splitting complex diffs into atomic commits. CX Codex +1 1,200installs commit parcadei This skill turns session changes into git commits, shows you the plan first, and keeps Claude's name out of the messages. Handy when an agent has piled up edits. CX Codex +1 499installs commit PaulRBerg Composes the commit message from prepared evidence and hands the commit, index reconciliation and push to ai-commit. CX Codex +1 342installs commit LegendApp Turns the changes from your current task into one or more tidy commits and keeps unrelated work out. Handy when the working tree has piled up several unrelated edits. CX Codex +1 404installs triage Matt Pocock This skill moves issues and external PRs through triage states, verification, and agent briefs. It fits maintainers managing an issue queue. 990,453installs code-review Matt Pocock Reviews changes from a chosen reference point against repository standards and the originating spec. Use it for a branch, PR, or work in progress. 789,521installs implement Matt Pocock Implements work from a specification or tickets, following a test-driven flow and ending with review and a commit. Use it when a coding task needs a defined delivery routine. 774,700installs git-guardrails-claude-code Matt Pocock This skill adds a Claude Code hook that stops risky Git commands before they run. Use it when an agent must not push or discard working-tree changes. 499,069installs setup-pre-commit Matt Pocock This skill configures pre-commit checks for a JavaScript repository, running Prettier, type checking, and tests before each commit. 489,289installs scaffold-exercises Matt Pocock This skill builds course exercise directories with sections, problems, solutions, and explainers. Use it when starting a new course section or creating exercise stubs. 480,196installs

From the same set3

review-pr Walks a branch diff against a checklist: bugs, security, performance, tests. Ends with a verdict — approve, request changes or discuss. CX Codex +1 ★ 116repo stars file-reading A routing skill that tells the agent which tool to reach for when a file is uploaded but its contents are not in context. CX Codex +1 ★ 116repo stars