commit
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`).
ronaknnathani · AI review on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add ronaknnathani/relay --skill commitAbout this skill
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 unstagedgit diff HEAD— the full staged and unstaged diffgit branch --show-current— the current branchgit log --oneline -10— recent commit message style to match
Create the commit
Based on the changes above, create one commit:
-
Stage the relevant files with
git add <specific-files>(stage the files this change touches, not unrelated work). -
Read
<repo>/AGENTS.mdand~/.config/agents/AGENTS.mdif present, then write a clear, concise commit message that matches those preferences and the repository's existing style. Lead with what changed and why. -
End the commit message with a
Co-authored-bytrailer 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. -
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.