Handles the commit, push, and memory synchronization of work in Egregore sessions.

Install

mkdir -p .claude/skills/save && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/17486" && unzip -o skill.zip -d .claude/skills/save && rm skill.zip

Installs to .claude/skills/save

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Save Egregore work when the user invokes /save or $save, or asks to commit, push, sync, or save current changes from a Codex Egregore session.
142 chars✓ has a “when” trigger
Beginner

Key capabilities

  • →Inspect repository and memory changes
  • →Synthesize a short topic and commit message
  • →Ask for scope confirmation if ambiguous
  • →Run the bridge command to save changes
  • →Report branch name, commit status, and PR URL

How it works

The skill inspects changes, synthesizes a commit message, confirms scope if needed, and then runs a bridge command to sync memory, commit repo changes, and push.

Inputs & outputs

You give it
User's request to save current changes or commit work
You get back
A report on the save operation, including branch name, commit status, and PR URL

When to use save

  • →Save current session
  • →Sync memory with git
  • →Push project changes

About this skill

<!-- generated-by: bin/codex-sync-skills.sh -->

Egregore save Adapter

This adapter runs the canonical Egregore workflow for save. Its one maintained body is .claude/skills/save/SKILL.md; read that file completely and follow it here.

Use the project shell and filesystem directly. Do not invoke Claude Code commands. Translate interactive choices to structured Codex question tooling when it is available; otherwise render compact numbered choices with an Other: option and wait for the user.

  1. Read .claude/skills/save/SKILL.md for the workflow details.
  2. Run the referenced bin/ scripts directly from Codex.
  3. Treat graph and publish steps as best-effort unless that workflow explicitly says they are required.
  4. For every external notification, follow .claude/context/notification-consent.md: plan without sending, then show a separate exact Send / Edit / Cancel checkpoint. Never infer notification consent from the workflow request or a batch approval.
  5. Keep local-mode behavior filesystem-first and avoid graph or notification calls when egregore.json declares "mode": "local".
  6. Never call the deprecated egregore-handoff CLI for Egregore project handoffs.

When not to use it

  • →When the user wants to run git commands directly
  • →When the user wants to expose implementation details

Limitations

  • →Does not ask the user to run git commands
  • →Does not expose implementation detail unless save fails
  • →Never runs destructive git commands

How it compares

This skill provides a user-facing abstraction for git and memory workflows, allowing users to save without knowing underlying commands, unlike manual git operations.

Compared to similar skills

save side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
save (this skill)04moReviewBeginner
tmux205moReviewIntermediate
jira119moNo flagsBeginner
triaging-issues55moReviewIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

Search skills

Search the agent skills registry