Create a single well-formed git commit from the working changes, following the repo's AGENTS.md and recent commit-message conventions. Use when the caller wants only to commit — not push and not open a PR (for that, use `open-pr`).
Installs into .claude/skills of the current project.
Are you the author of Commit?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/ronaknnathani-commit)
---
name: commit
description: Create a single well-formed git commit from the working changes, following the repo's AGENTS.md and recent commit-message conventions. Use when the caller wants only to commit — not push and not open a PR (for that, use `open-pr`).
---
# Commit
Create a single git commit for the current changes.
## Gather context
First inspect the working tree. Run these read-only commands and read their output:
- `git status` — what is staged and unstaged
- `git diff HEAD` — the full staged and unstaged diff
- `git branch --show-current` — the current branch
- `git log --oneline -10` — recent commit message style to match
## Create the commit
Based on the changes above, create one commit:
1. Stage the relevant files with `git add <specific-files>` (stage the files this change touches, not unrelated work).
2. Read `<repo>/AGENTS.md` and `~/.config/agents/AGENTS.md` if present, then write a clear, concise commit message that matches those preferences and the repository's existing style. Lead with what changed and why.
3. End the commit message with a `Co-authored-by` trailer for the actual model/agent currently doing the work. Use the runtime-provided model identity when available, and the agent's verified no-reply identity for the email. Never hardcode a model name.
4. Commit with `git commit`.
Use only `git add`, `git status`, and `git commit`. Do not push, do not run other tools, and do not take any other action.
