Stage changes and create a commit with a properly formatted message. Use for /commit, or saving work locally — not sharing it (/push) or opening a pull request (/pr).
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Stage changes and commit with a message.
User says: "/commit", "commit this", "stage and commit", "save this change locally"
Not this: sharing your commit with others → /push · opening a pull request → /pr
Message (optional): $ARGUMENTS
This is a deterministic Git operation. Run it inline through the shared Git mechanics; do not spend a Loom/model-routing call or delegate it to another agent. Judgment is limited to selecting relevant files and composing the message.
Resolve the base with bash bin/base-branch.sh (add the managed repo name when
applicable); it prints {base} or fails, in which case stop.
Check git branch --show-current. If on a protected branch ({base}, develop,
main, or master):
→ Use the resolved base branch (default "develop")
→ Create a working branch: git fetch origin "{base}" --quiet, then
git checkout --no-track -b dev/{author}/{topic-slug} "origin/{base}"
→ Tell the user: "Creating a working branch for this..." — never mention git commands to the user.
→ Then proceed with the commit.
Full spec: .claude/context/commit-format.md. Wording:
.claude/context/git-language.md. The short form:
Subject type(scope): imperative summary — ≤ 72 chars (aim ≤ 50),
lowercase, no trailing period. Same grammar and type set as PR
titles. It completes "if applied, this commit will ___".
Body (when the diff cannot explain its own motivation): blank line after the subject, wrapped at 72, what and why — never how.
Agent-authored commits end with a trailer block as the final paragraph:
cat .egregore-session-id
git commit -m "feat(mcp): add API key authentication" -m "Egregore-Session: {session-id}
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>"
Read the id with the first command (a plain command) and paste it as
{session-id}. When the file is absent, omit the Egregore-Session line;
use your harness's own identity line. Humans committing by hand skip trailers.
One logical change per commit — split when the parts are independently revertable.
> /commit
Checking changes...
Modified files:
src/mcp/auth.py (+42, -3)
src/mcp/server.py (+8, -2)
tests/test_auth.py (+28, new file)
Untracked:
src/mcp/__pycache__/ (ignored ✓)
Staging modified files...
git add src/mcp/auth.py src/mcp/server.py tests/test_auth.py
Enter commit message (or I can suggest one):
> feat(mcp): add API key authentication
git commit -m "feat(mcp): add API key authentication" # + trailer block
✓ Committed (abc1234)
Changes committed locally. Run /push to share, or /pr when ready for review.
> /commit docs(readme): fix typo
Staging and committing...
git add -A
git commit -m "docs(readme): fix typo"
✓ Committed (def5678)
Run /push to share, or keep working and commit again.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Explicit Activity card only. Use when the user names /activity or directly asks to show, open, or render the Activity dashboard/card. Never use it to answer or synthesize what the team is focused on, busy with, prioritizing, or doing; analytical organizational questions use Search/Runtime QMD.
The English summary is being prepared. Showing the original description.
Draft, preview, and explicitly send an Egregore group announcement. Use for /announce, telling the team something, or notifying everyone—not a direct message or structured handoff.
The English summary is being prepared. Showing the original description.
Capture an effective prompting or steering technique as a reusable canonical pattern. Use when a prompt chain worked especially well; use /reflect for insight about the work and /note for a private thought.
The English summary is being prepared. Showing the original description.
Create a working branch from what you are about to work on. Use for /branch, or any request to start a new branch before making changes.
The English summary is being prepared. Showing the original description.
Run diagnostics on an Egregore environment and render a health report, repairing safe local Runtime problems when possible. Use for /checkup, a health check, or when something is broken and the root cause is unclear.
The English summary is being prepared. Showing the original description.
Contribute an improvement back to the upstream Egregore framework as a cross-fork pull request. Use for /contribute, or submitting a framework fix upstream — not saving org work (/save) or filing a bug (/issue).
The English summary is being prepared. Showing the original description.