React Router Release Notes Prep
remix-run/react-router
Polishes pending React Router change files before the versioning scripts run, and decides whether a long-form What's Changed section is warranted.
Create a git commit with a short message that describes the diff.
Install Commit
$ npx skills add gweslab/cerf --skill commit -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install gweslab/cerf commit --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/gweslab/cerf.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/commit .claude/skills/commit && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "commit" agent skill from https://github.com/gweslab/cerf/tree/main/.claude/skills/commit into .claude/skills/commit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "commit", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/gweslab/cerf/tree/main/.claude/skills/commitType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add gweslab/cerf --skill commit -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install gweslab/cerf commit --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gweslab/cerf.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/commit .agents/skills/commit && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "commit" agent skill from https://github.com/gweslab/cerf/tree/main/.claude/skills/commit into .agents/skills/commit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "commit", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add gweslab/cerf --skill commit -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install gweslab/cerf commit --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gweslab/cerf.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/commit .cursor/skills/commit && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "commit" agent skill from https://github.com/gweslab/cerf/tree/main/.claude/skills/commit into .cursor/skills/commit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "commit", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/gweslab/cerf.git --path .claude/skills/commit--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add gweslab/cerf --skill commit -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install gweslab/cerf commit --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gweslab/cerf.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/commit .gemini/skills/commit && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "commit" agent skill from https://github.com/gweslab/cerf/tree/main/.claude/skills/commit into .gemini/skills/commit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "commit", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install gweslab/cerf commitInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add gweslab/cerf --skill commit -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/gweslab/cerf.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/commit .github/skills/commit && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "commit" agent skill from https://github.com/gweslab/cerf/tree/main/.claude/skills/commit into .github/skills/commit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "commit", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add gweslab/cerf --skill commit -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install gweslab/cerf commit --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gweslab/cerf.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/commit .opencode/skills/commit && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "commit" agent skill from https://github.com/gweslab/cerf/tree/main/.claude/skills/commit into .opencode/skills/commit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "commit", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
commit- GitHub stars
- 103
- Token cost
- ~1.2k tokens
- SKILL.md length
- 778 words
- Files
- 1
- Skills in repo
- 11
- Repo updated
- First seen
- Licence
- MIT
At a glance
Create a git commit with a short message that describes the diff.
- Works in 3 steps: Run git status, then git diff (staged… → Stage only the paths this work touched. → Commit with a message written under the…
- Tasks that involve Commit messages
- SKILL.md covers Procedure, The message, Example and Forbidden, plus 3 more sections
- Calls git
What it does
Commit is an agent skill from gweslab/cerf. Create a git commit with a short message that describes the diff.
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Commit messages. It works with Git. The repository describes itself as: Universal Windows CE Emulator - CE Runtime Foundation. The licence is MIT.
When your agent uses it
- Tasks that involve Commit messages
Example prompts
- “/commit”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Run git status, then git diff (staged and unstaged). Read what actually changed.
- Stage only the paths this work touched.
- Commit with a message written under the rules below.
What it can do on your machine
Read from SKILL.md and the folder at commit 462ed3d. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Commit loads about 1.2k tokens when it runs. Until then it costs about 18 tokens; SKILL.md has 778 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from gweslab/cerf at commit 462ed3d, republished under its MIT licence (© gweslab). 778 words, ~1,213 tokens.
Download SKILL.mdSave it as
.claude/skills/commit/SKILL.md (or your agent's skills folder).- name
- commit
- description
- Create a git commit with a short message that describes the diff.
Commit - short, leak-free git commit
Someone reads this message years from now, with no knowledge of this conversation. They want one thing: what changed. Every other sentence is noise you are asking that reader to skip.
Fewer words is better. A one-line title is the target, not a minimum.
Procedure
- Run
git status, thengit diff(staged and unstaged). Read what actually changed. - Stage only the paths this work touched.
- Commit with a message written under the rules below.
The message
- Describe the diff, not the discussion. The message covers what the change does to the project. It never covers the conversation that produced it.
- A body is banned. Write the one-line title, then stop. If you judge a body "substantive", "justified", or "short enough", that judgment IS the slop. Delete it. Ship the title.
- Use the imperative, with a lowercase scope prefix that matches recent commits (
jornada820: keyboard,host: compose window title from cerf.json device meta). Readgit logfirst. - End with the
Co-Authored-By:trailer for the model that runs this session. Claude Code supplies it.
Example
One diff, two messages:
Slop:
fix: resolve the LCD issueAs you asked, this commit fixes the display bug we found. I first tried changing the palette, but you were right that the real problem was elsewhere. This took several attempts to get correct.
Clean:
s3c2410: latch LCD palette at frame start
The clean message tells the reader what changed. The slop message tells them about a Tuesday afternoon.
Forbidden
- A body that restates the diff - a summary of the mechanism, a list of the parts touched, an expansion of the title. It is accurate, which is why it feels safe to write. The title already said what changed, and the diff says the rest.
Each of these describes the session instead of the diff:
- Conversation echoes - "as you asked", "per your feedback", "you were right", "reverted per discussion".
- Narration - "this commit", "in this change we", an essay about a one-line edit, "renamed the section", the name of a section you deleted.
- Incident history - "this broke 3 times", "after the regression".
- Alternatives - "we chose X over Y", "originally tried Z".
- Agent or session references - "the previous agent", "a prior session". The trailer is the only sanctioned model mention.
- Private design leaks - section numbers (
§3.1), phase names,docs/ai_checklists/paths, any vocabulary from a checklist. Those files are confidential and never enter git history. - Personal data leak - "John Smith told to do this".
The test for a line: a developer at a fresh clone, who never saw this session, understands it. If a line makes sense only to someone who watched the conversation, delete it.
Show full SKILL.md (334 more words)Show less
GitHub issues
An issue reference is diff metadata, so it is welcome. When the commit fully resolves the issue, put Fixes #123 on its own line above the trailer. When the commit is related but does not resolve it, use Refs #123. Reference an issue only when the diff corresponds to it. The issue thread is still conversation, so do not summarize it into the body.
CI keywords
The default is no keyword. A commit carries a keyword only when the user asks for that CI action.
Three keywords in the commit message start a CI action. CI reads the full message. Put the keyword at the end of the title line.
[skip build]- CI does not build this commit.[rc]- CI announces the artifact on the QA Discord channel as a release candidate. Every member of the channel receives a notification.[release cerf]- CI publishes the artifact as a release on all platforms. The release is public, and users download it.
When the user asks for one of these actions directly, write its keyword. The request "/commit a release build" names the release action, so write [release cerf]. When the user asks for no action, write no keyword.
When you write a keyword, tell the user in bold immediately after the commit. Name the action that CI will do.
This commit has
[release cerf]. CI will publish a release on all platforms.
If your reading of the request is incorrect, the user sees that line and stops you.
Hard stops
- Never run git unless the user asked.
/commitis that ask, and it covers this one commit. Do notgit push, which needs separate approval. - Never force past
.gitignorewithgit add -f. The ignore is a STOP signal. - Stage only what this session changed. Other agents and the user work in this tree at the same time, so
git statusoften lists edits that are not yours. If you did not make a change, leave it unstaged and say it is there.
© gweslab, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .claude/skills/commit of gweslab/cerf.
Open the folder on GitHubat commit 462ed3d
Compare with similar skills
Commit next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Commit this skillgweslab/cerf | 103 | — | ~1.2k | Automated safety check: Pass | MIT | |
| React Router Release Notes Prepremix-run/react-router | 57k | — | ~1.1k | Automated safety check: Pass | MIT | |
| ToolJet Multi-Repo CommitToolJet/ToolJet | 41k | — | ~1.3k | Automated safety check: Pass | AGPL-3.0 | |
| Git Workflow and Versioningaddyosmani/agent-skills | 102k | 2 repos | ~3.5k | Automated safety check: Notes | MIT | |
| React Router Pull Request Creatorremix-run/react-router | 57k | — | ~2.5k | Automated safety check: Pass | MIT | |
| Verdaccio Pull Request Workflowverdaccio/verdaccio | 18k | — | ~1.9k | Automated safety check: Pass | MIT |
Similar skills
ToolJet Multi-Repo Commit
ToolJet/ToolJet
Commits changes across ToolJet's root repo and its server/ee and frontend/ee submodules, writing messages from the diffs and updating submodule pointers in order.
Git Workflow and Versioning
addyosmani/agent-skills
Sets git habits for every change: short-lived branches, atomic commits with descriptive messages, clean pull requests, plus versioning, tagging and changelogs for releases.
React Router Pull Request Creator
remix-run/react-router
Packages finished React Router work into a draft pull request: branch, commit, push, a written PR body and the right GitHub labels.
Verdaccio Pull Request Workflow
verdaccio/verdaccio
Takes a change through a verdaccio pull request: branch, local checks, changeset, title and body, labels, CI and review rounds, and ports to other release lines.
Saleor Commit Workflow
saleor/saleor
Commits changes in the Saleor codebase and works through pre-commit hook failures from ruff, mypy, the GraphQL schema check and the migrations check.
More from gweslab/cerf
All 11 skills in this repoCerf
gweslab/cerf
List the project skills and offer the environment doctor. An agent skill from gweslab/cerf.
Changelog Append
gweslab/cerf
Add a changelog entry for a change that was just made (only user triggered, no agent self-invocation).
Start Board Implementation
gweslab/cerf
Start the bring-up of a new board or ROM in CERF. An agent skill from gweslab/cerf.
Tracking
gweslab/cerf
Manage the cross-session tracking document with restore, create, update, or compact (only user triggered, no agent self-invocation).
Verify
gweslab/cerf
Spawn a hostile reviewer that checks a claim or a diff against the project rules.
Verify Options
gweslab/cerf
Audit a list of options for bailouts and rule violations before the user picks one.
Related
Works with
Categories
Questions about Commit
What does Commit do?
Create a git commit with a short message that describes the diff. Commit is an agent skill from gweslab/cerf. Create a git commit with a short message that describes the diff.
When should I use Commit?
Commit fits situations like: tasks that involve Commit messages.
How do I install Commit in Claude Code?
Run `npx skills add gweslab/cerf --skill commit -a claude-code`. Or copy the skill folder (.claude/skills/commit in gweslab/cerf) into .claude/skills/commit in your project. Claude Code loads it when a task matches its description.
How do I install Commit in Codex?
Run `npx skills add gweslab/cerf --skill commit -a codex`. Or copy the skill folder (.claude/skills/commit in gweslab/cerf) into .agents/skills/commit in your project. Codex loads it when a task matches its description.
Can I use Commit in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add gweslab/cerf --skill commit -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/commit, .gemini/skills/commit, .github/skills/commit and .opencode/skills/commit in your project.
What does Commit need to run?
Going by SKILL.md and its folder, Commit needs the command-line tools its instructions call (git).
Does Commit access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Commit safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Commit use?
Commit is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Commit use?
About 1.2k tokens (SKILL.md is roughly 4.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Commit?
Skills that share tags, products or a category with Commit: React Router Release Notes Prep (remix-run/react-router, 57k stars), ToolJet Multi-Repo Commit (ToolJet/ToolJet, 41k stars), Git Workflow and Versioning (addyosmani/agent-skills, 102k stars) and React Router Pull Request Creator (remix-run/react-router, 57k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Commit?
gweslab (a GitHub organization) maintains it in gweslab/cerf, which has 103 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 7, 2026.
Source: gweslab/cerf on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.