Git Commit
SkillCommunicationCreate 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.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Git Commit skill
What this skill tells your AI
The instructions your AI receives, as published by seifbenayed/cloclo in .claude/skills/commit/SKILL.md and read by ahel’s review.
Review all staged changes and create a well-crafted commit message.
Steps
- Run
git statusto see staged and unstaged changes - Run
git diff --cachedto review staged changes in detail - If nothing is staged, run
git diffand suggest what to stage based on the changes - Run
git log --oneline -5to see recent commit message style in the repo - Draft a concise commit message following conventional commits format:
feat:— new featurefix:— bug fixrefactor:— code restructuring without behavior changedocs:— documentation changestest:— adding or updating testschore:— 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
Signals
- GitHub stars
- 114
- Forks
- 30
- Last commit
- Apr 2026
Advanced
- Catalog kind
- skill
- Gateway key
commit-seifbenayed- Source
- github.com/seifbenayed/cloclo