Commit
Skills to orchestrate coding agents to do long horizon tasks with little to no steering
npx -y skills add ronaknnathani/relay --skill commitAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
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`).
SKILL.md
1.4 KB, as published. Nobody here has run it
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.