Agent skill

Ce Commit

by EveryInc in EveryInc/compound-engineering-plugin

Create a git commit with a clear, value-communicating message.

MITAuto-check passedDevelopment

Install Ce Commit

skills CLI

$ npx skills add EveryInc/compound-engineering-plugin --skill ce-commit -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install EveryInc/compound-engineering-plugin ce-commit --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/EveryInc/compound-engineering-plugin.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/ce-commit .claude/skills/ce-commit && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "ce-commit" agent skill from https://github.com/EveryInc/compound-engineering-plugin/tree/main/skills/ce-commit into .claude/skills/ce-commit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ce-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

$skill-installer install https://github.com/EveryInc/compound-engineering-plugin/tree/main/skills/ce-commit

Type 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.

skills CLI

$ npx skills add EveryInc/compound-engineering-plugin --skill ce-commit -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install EveryInc/compound-engineering-plugin ce-commit --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/EveryInc/compound-engineering-plugin.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/ce-commit .agents/skills/ce-commit && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "ce-commit" agent skill from https://github.com/EveryInc/compound-engineering-plugin/tree/main/skills/ce-commit into .agents/skills/ce-commit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ce-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.

skills CLI

$ npx skills add EveryInc/compound-engineering-plugin --skill ce-commit -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install EveryInc/compound-engineering-plugin ce-commit --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/EveryInc/compound-engineering-plugin.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/ce-commit .cursor/skills/ce-commit && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "ce-commit" agent skill from https://github.com/EveryInc/compound-engineering-plugin/tree/main/skills/ce-commit into .cursor/skills/ce-commit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ce-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

$ gemini skills install https://github.com/EveryInc/compound-engineering-plugin.git --path skills/ce-commit

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add EveryInc/compound-engineering-plugin --skill ce-commit -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install EveryInc/compound-engineering-plugin ce-commit --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/EveryInc/compound-engineering-plugin.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/ce-commit .gemini/skills/ce-commit && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "ce-commit" agent skill from https://github.com/EveryInc/compound-engineering-plugin/tree/main/skills/ce-commit into .gemini/skills/ce-commit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ce-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.

GitHub CLI

$ gh skill install EveryInc/compound-engineering-plugin ce-commit

Installs 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).

skills CLI

$ npx skills add EveryInc/compound-engineering-plugin --skill ce-commit -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/EveryInc/compound-engineering-plugin.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/ce-commit .github/skills/ce-commit && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "ce-commit" agent skill from https://github.com/EveryInc/compound-engineering-plugin/tree/main/skills/ce-commit into .github/skills/ce-commit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ce-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.

skills CLI

$ npx skills add EveryInc/compound-engineering-plugin --skill ce-commit -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install EveryInc/compound-engineering-plugin ce-commit --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/EveryInc/compound-engineering-plugin.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/ce-commit .opencode/skills/ce-commit && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "ce-commit" agent skill from https://github.com/EveryInc/compound-engineering-plugin/tree/main/skills/ce-commit into .opencode/skills/ce-commit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ce-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: ce-commit
GitHub stars: 25k
Token cost: ~1.2k tokens
SKILL.md length: 668 words
Files: 1
Skills in repo: 37
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Create a git commit with a clear, value-communicating message.

Works in 7 steps: Gather — run every Context command above… → Nothing to commit — if git status shows… → Branch first — if detached HEAD, or on… → …
The user asks to commit/save staged
SKILL.md covers Context and Workflow
Calls git and gh

What it does

Ce Commit is an agent skill from EveryInc/compound-engineering-plugin. Create a git commit with a clear, value-communicating message. Use when the user asks to commit/save staged or unstaged changes with a repo-appropriate message.

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: Official Compound Engineering plugin for Claude Code, Codex, Cursor, and more. The licence is MIT.

When your agent uses it

The user asks to commit/save staged
Unstaged changes with a repo-appropriate message

Example prompts

“/ce-commit”

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

Gather — run every Context command above (own shell call each), then continue.
Nothing to commit — if git status shows no staged, modified, or untracked files, report that and stop. Do not use git diff HEAD alone as…
Branch first — if detached HEAD, or on the default branch (main / master / the bare default name above), create a feature branch from the…
Convention — match project commit conventions already in context; else match the recent log pattern; else conventional commits…
Logical commits — if changed files clearly split into distinct concerns, make separate commits (file level only, 2–3 max, no git add -p)…
Message — subject is imperative and names the outcome (what is now possible or fixed), not the file list. Body only when motivation or…
Stage and commit — stage named files only (never git add -A or git add .). Honor exclude: when the invocation carries it: those files stay…

What it can do on your machine

Read from SKILL.md and the folder at commit cef001f. 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
- gh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git and gh, 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

Ce Commit loads about 1.2k tokens when it runs. Until then it costs about 43 tokens; SKILL.md has 668 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~43
When it runs · the whole SKILL.md, loaded when a task matches: ~1.2k

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 EveryInc/compound-engineering-plugin at commit cef001f, republished under its MIT licence (© EveryInc). 668 words, ~1,185 tokens.

Download SKILL.mdSave it as .claude/skills/ce-commit/SKILL.md (or your agent's skills folder).

name: ce-commit
description: Create a git commit with a clear, value-communicating message. Use when the user asks to commit/save staged or unstaged changes with a repo-appropriate message.

Git Commit

Create well-crafted local commit(s) from the current working tree. No push, no PR — use ce-commit-push-pr for the full ship flow.

Done when: each logical change is committed with an explicit file list and a message that states the outcome, and git status is clean of those changes. Stop when: the tree is clean (nothing to commit).

Context

Gather context with each command as its own shell tool call (program + args only). Do not join with ;, &&, ||, pipes, $(...), or redirects — that syntax fails under Windows PowerShell. A non-zero exit is a normal state to interpret, not a failure to suppress.

Command	Purpose	Non-zero / empty means
`git status`	Working-tree state	Not a git repo — stop
`git diff HEAD`	Uncommitted changes	Unborn repo / no commits yet
`git branch --show-current`	Current branch	Empty = detached HEAD
`git log --oneline -10`	Recent message style	Unborn repo — no history
`git rev-parse --abbrev-ref origin/HEAD`	Remote default branch	No `origin/HEAD` / bare `HEAD` — try `gh repo view --json defaultBranchRef --jq '.defaultBranchRef.name'`, else `main`

Treat this as a snapshot. Re-read branch and staged set immediately before committing if anything may have changed.

Default branch name: strip a leading origin/ from origin/HEAD (so origin/trunk → trunk). Use that bare name for all “on the default branch?” checks — never compare against origin/<name>.

Workflow

Gather — run every Context command above (own shell call each), then continue.
Nothing to commit — if git status shows no staged, modified, or untracked files, report that and stop. Do not use git diff HEAD alone as cleanliness (it misses untracked files).
Branch first — if detached HEAD, or on the default branch (main / master / the bare default name above), create a feature branch from the change content (git checkout -b <name>), then re-read git branch --show-current. Do not ask — commit-only still must not leave work only on a detached HEAD or the default branch. If the derived name exists, pick a non-conflicting suffix.
Convention — match project commit conventions already in context; else match the recent log pattern; else conventional commits (type(scope): description). When using conventional commits and fix/feat both fit, default to fix: (remedying broken or missing behavior); reserve feat: for new capabilities. User override wins.
Logical commits — if changed files clearly split into distinct concerns, make separate commits (file level only, 2–3 max, no git add -p). If ambiguous, one commit.
Message — subject is imperative and names the outcome (what is now possible or fixed), not the file list. Body only when motivation or trade-offs are not obvious from the subject. When a plan Implementation Unit ID is already in hand for this commit (conversation, caller, or the files belong to one unit), append that unit's U-ID in parentheses — (U3) means unit 3. Do not hunt for a plan. Omit when the commit spans units, the unit is unclear, or no plan is in hand.
- Bad: Update checkout.rb / Add tests and fix stuff
- Good: Fix double-submit on checkout
- Good: Add per-subscription mute (U3)
Stage and commit — stage named files only (never git add -A or git add .). Honor exclude:<paths> when the invocation carries it: those files stay uncommitted no matter what else changed; say in the report that they were left out. Write the full message — subject line, blank line, optional body — to a file outside the repo with your file-write tool, then stage and commit as two calls per commit group:

Show full SKILL.md (108 more words)Show less

bash

git add file1 file2 file3

bash

git commit -F <message-file> -- file1 file2 file3

No shell parses the message with -F: a $, quotes, backticks, or a multi-line body pass through literally under any shell, with no quoting rules to satisfy. Git's normal whitespace cleanup still applies (trailing spaces trimmed, blank-line runs collapsed), which is fine for a commit message.

The trailing path list on git commit is required: a bare git commit takes the whole index, so anything already staged before this run (a caller's exclude: paths, or work the user staged and did not name) would ride into the commit. Naming the paths commits exactly the group and leaves other index entries alone.

Confirm — git status; report hash(es) and subject(s).

Files

Just SKILL.md in skills/ce-commit of EveryInc/compound-engineering-plugin.

Open the folder on GitHubat commit cef001f

Compare with similar skills

Ce 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.

Ce Commit compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Ce Commit this skillEveryInc/compound-engineering-plugin	25k	—	~1.2k	Automated safety check: Pass	MIT	today
React Router Release Notes Prepremix-run/react-router	57k	—	~1.1k	Automated safety check: Pass	MIT	today
ToolJet Multi-Repo CommitToolJet/ToolJet	41k	—	~1.3k	Automated safety check: Pass	AGPL-3.0	today
Git Workflow and Versioningaddyosmani/agent-skills	102k	2 repos	~3.5k	Automated safety check: Notes	MIT	4 days ago
React Router Pull Request Creatorremix-run/react-router	57k	—	~2.5k	Automated safety check: Pass	MIT	today
Verdaccio Pull Request Workflowverdaccio/verdaccio	18k	—	~1.9k	Automated safety check: Pass	MIT	today

Similar skills

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.
57k GitHub stars~1.1k tokensUpdated today
DevelopmentAuto-check passed
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.
41k GitHub stars~1.3k tokensUpdated today
DevelopmentAuto-check passed
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.
102k GitHub starsUsed in 2 repos~3.5k tokens
DevelopmentAuto-check: notes
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.
57k GitHub stars~2.5k tokensUpdated today
DevelopmentAuto-check passed
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.
18k GitHub stars~1.9k tokensUpdated today
DevelopmentAuto-check passed
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.
23k GitHub stars~575 tokensUpdated yesterday
DevelopmentAuto-check passed

More from EveryInc/compound-engineering-plugin

All 37 skills in this repo

Compound Learning Writer
EveryInc/compound-engineering-plugin
Records one solved and verified problem as a durable learning in the repository, but only when the reasoning is not already clear from the final code, tests or docs.
25k GitHub stars~2k tokensUpdated today
Auto-check passed
Compound Learnings Refresh
EveryInc/compound-engineering-plugin
Audits a repo's stored learnings against the current codebase, fixes stale, overlapping or superseded docs and reports on every document.
25k GitHub stars~2k tokensUpdated today
Auto-check passed
Compound Engineering Prototype
EveryInc/compound-engineering-plugin
Builds a throwaway prototype at just the fidelity needed to settle a specific how-it-should-work-or-feel question, before committing to an approach other work will treat as fixed.
25k GitHub stars~1.9k tokensUpdated today
Auto-check passed
Compound Engineering Setup
EveryInc/compound-engineering-plugin
Checks Compound Engineering plugin health and repo-local config, or scaffolds a Compound Pack when you ask for one by id.
25k GitHub stars~1.9k tokensUpdated today
Auto-check passed
PR Babysitter
EveryInc/compound-engineering-plugin
Watches an open GitHub pull request over time, routing review comments and CI failures to other skills until the PR is ready to merge.
25k GitHub stars~2k tokensUpdated today
Auto-check passed
CE Brainstorm
EveryInc/compound-engineering-plugin
Turns a vague or ambitious feature idea into a requirements-only plan through dialogue with you, sized to the work, before any code is written.
25k GitHub stars~1.9k tokensUpdated today
Auto-check passed

Works with

Questions about Ce Commit

What does Ce Commit do?

Create a git commit with a clear, value-communicating message. Ce Commit is an agent skill from EveryInc/compound-engineering-plugin. Create a git commit with a clear, value-communicating message.

When should I use Ce Commit?

Ce Commit fits situations like: the user asks to commit/save staged; unstaged changes with a repo-appropriate message.

How do I install Ce Commit in Claude Code?

Run `npx skills add EveryInc/compound-engineering-plugin --skill ce-commit -a claude-code`. Or copy the skill folder (skills/ce-commit in EveryInc/compound-engineering-plugin) into .claude/skills/ce-commit in your project. Claude Code loads it when a task matches its description.

How do I install Ce Commit in Codex?

Run `npx skills add EveryInc/compound-engineering-plugin --skill ce-commit -a codex`. Or copy the skill folder (skills/ce-commit in EveryInc/compound-engineering-plugin) into .agents/skills/ce-commit in your project. Codex loads it when a task matches its description.

Can I use Ce 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 EveryInc/compound-engineering-plugin --skill ce-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/ce-commit, .gemini/skills/ce-commit, .github/skills/ce-commit and .opencode/skills/ce-commit in your project.

What does Ce Commit need to run?

Going by SKILL.md and its folder, Ce Commit needs the command-line tools its instructions call (git and gh).

Does Ce Commit access the network?

SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Ce 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 Ce Commit use?

Ce 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 Ce Commit use?

About 1.2k tokens (SKILL.md is roughly 4.7k 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 Ce Commit?

Skills that share tags, products or a category with Ce 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 Ce Commit?

EveryInc (a GitHub organization) maintains it in EveryInc/compound-engineering-plugin, which has 25,412 GitHub stars. The repository holds 37 skills in this directory. The repository was last updated on October 7, 2026.

Source: EveryInc/compound-engineering-plugin on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Ce Commit

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Git Commit

Context

Workflow

Files

Compare with similar skills

Similar skills

More from EveryInc/compound-engineering-plugin

Related

Questions about Ce Commit