Claude-code-sdk commit

Name: commit
Author: SeifBenayed

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.

install

source · Clone the upstream repo

git clone https://github.com/SeifBenayed/cloclo

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/SeifBenayed/cloclo "$T" && mkdir -p ~/.claude/skills && cp -r "$T/.claude/skills/commit" ~/.claude/skills/seifbenayed-claude-code-sdk-commit && rm -rf "$T"

manifest: .claude/skills/commit/SKILL.md

source content

Git Commit

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

Steps

Run
```
git status
```
to see staged and unstaged changes
Run
```
git diff --cached
```
to review staged changes in detail
If nothing is staged, run
```
git diff
```
and suggest what to stage based on the changes
Run
```
git log --oneline -5
```
to see recent commit message style in the repo
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
Focus the message on why not what — the diff shows what changed
Keep the first line under 72 characters
Add a body paragraph if the change is non-trivial
Create the commit

Do NOT push unless explicitly asked. Do NOT use

--no-verify

or skip hooks.

$ARGUMENTS