Commit Changes
SkillCommunicationGenerate a commit message based on current changes and commit all staged and unstaged changes to git
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 Commit Changes skill
What this skill tells your AI
The instructions your AI receives, as published by ok-oldking/ok-script in .agents/skills/commit_changes/SKILL.md and read by ahel’s review.
When instructed to commit changes, follow these steps:
1. Check for uncommitted changes
// turbo
git status --short
If there are no uncommitted changes (no output from the command above), tell the user "No uncommitted changes to commit." and STOP.
2. Review changes and generate a commit message
// turbo
git diff --stat
// turbo
git diff
Review the output of git diff and git diff --stat. Write a concise, descriptive commit message summarizing only these uncommitted changes. The message should:
- Use imperative mood (e.g. "Add …", "Fix …", "Refactor …")
- Be a single line for simple changes.
- For complex changes, use a single summary line, followed by a blank line and bullet points.
3. Stage and commit all changes
// turbo
git add -A
// turbo
git commit -m "<generated commit message>"
Replace <generated commit message> with the message you wrote in step 2.
4. Report
Tell the user:
- The commit message used.
- A brief summary of what was committed.
Signals
- GitHub stars
- 731
- Forks
- 203
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
commit-ok-oldking- Source
- github.com/ok-oldking/ok-script