update
Skill293 starsChanged 10 days agoMITView on GitHub
Update local Egregore environment — sync the framework from upstream, run post-update migrations, and pull repos. Use for /update or when framework behavior seems broken or missing.
- Reads credentials
- Commits and pushes
65 other projects use a version of this.
Adopted by
Most recently taken up by
- finolabs/finolabs-vibecodetheir own version, first seen Nov 16, 2026
- patrickjaja/claude-desktop-extratheir own version, first seen Nov 15, 2026
- FYClamityDestiny/vettedtheir own version, first seen Nov 15, 2026
- shivasaini04/nanocrewtheir own version, first seen Nov 15, 2026
- finolabs/vibecodetheir own version, first seen Nov 15, 2026
- ivy/dotfilestheir own version, first seen Nov 13, 2026
Used with
Projects with it also use end, create and 8 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
torarnvSkillend
Wrap up a work session. Updates memory files, logs decisions and lessons, appends to the session log.
Also in 3 projects that use this
MicrosoftSkillcreate
Also in 4 projects that use this
kv0906Skillinbox
Quick capture mode (with content) or batch processing mode (no content). GTD-style routing of inbox items to proper folders. Use "/inbox thought to capture" or "/inbox" to process.
Also in 4 projects that use this
jholhewresSkillbackup
Backup and restore — files, databases, and system backups
Also in 3 projects that use this
SidUSkilltoday
Plan today's work using this repo's workflow. Use when the user asks for /today or phrases like "plan my day", "today's plan", "set my priorities", or "start my day".
Also in 3 projects that use this
MicrosoftSkillhelp
Entry point for the MedImageInsight plugin, covering the getting-started walkthrough, how the skills work, what MI2 is, and troubleshooting.
Also in 6 projects that use this
- +1 more from microsoft
Other versions65 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 65
- anthropics/knowledge-work-plugins★ 36ksame name
- Q00/ouroboros★ 6.4ksame name
- vellum-ai/vellum-assistant★ 1.5ksame name
- patrickjaja/claude-desktop-extra★ 761same name
- me2resh/apexyard★ 542same name
- daloopa/investing★ 488same name
- TokenRollAI/cc-plugin★ 483same name
- k1p1l0/claude-telegram-supercharged★ 144same name
- kv0906/pm-kit★ 138same name
- buildomator/buildomator★ 102same name
55 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository50 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- activitySkill
- announceSkill
- archiveSkill
- branchSkill
- checkupSkill
- commitSkill
- contributeSkill
- create-skillSkill
- dark-modeSkill
- dashboardSkill
- deep-reflectSkill
- delete-userSkill
- emissarySkill
- envSkill
- handoffSkill
- harvestSkill
- ingest-corpusSkill
- ingest-notionSkill
- ingestSkill
- ingest-user-interviewSkill
- inviteSkill
- issueSkill
- meetingSkill
- meSkill
- noteSkill
- notion-connectSkill
- onboardingSkill
- prSkill
- pullSkill
- pushSkill
- questSkill
- recordsSkill
- reflectSkill
- review-prSkill
- saveSkill
- slack-connectSkill
- summonSkill
- sync-reposSkill
- telegram-connectSkill
- telemetrySkill
- testSkill
- the-spiralSkill
- tui-designSkill
- tutorialSkill
- viewSkill
- visual-explainSkill
- wrapSkill
- preview-designSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
23 rules. 0 are common, 2 are distinctive, and 21 are very specific to this project.
0
Common
Most of the 63 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
21
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 6
Update local Egregore environment — sync framework from upstream and pull repos.
- Very specific: line 11
Not this: syncing managed repos + memory only, no framework sync → /pull
- Very specific: line 28
Use the printed branch name as {base}.
- Very specific: line 34
Use the printed branch as {current_branch} for the non-worktree switch and restore steps.
- Very specific: line 41
Use true as {in_worktree} if the test exits successfully.
- Very specific: line 47
Use the printed common Git directory's parent as {main_dir}, the main checkout.
- Very specific: line 59
Use the printed value as {upstream_url}.
- Very specific: line 72
Use {upstream_url} as {upstream} when set.
- Very specific: line 75
If {in_worktree} is true, ensure the upstream remote exists in the main checkout:
- Very specific: line 81
If it reports that the remote already exists, run git -C '{main_dir}' remote set-url upstream '{upstream}' instead.
- Very specific: line 87
If {in_worktree} is false, ensure the upstream remote exists in this checkout:
- Very specific: line 101
If {in_worktree} is true, sync framework paths only in the named main checkout:
- Very specific: line 107
Stop if the command fails: the target checkout, upstream remote, and fetched upstream/main must exist.
- Very specific: line 142
If {in_worktree} is false, use false as {switched} initially.
- Very specific: line 153
After switching successfully, use true as {switched} for Step 4.
- Very specific: line 155
If {in_worktree} is false, sync the same framework paths in this checkout:
- Distinctive: line 161
Stop on failure as in the worktree path, then continue the non-worktree path:
- Very specific: line 187
If {in_worktree} is false, show the changes before continuing:
- Very specific: line 203
After syncing, run the updated bin/post-update.sh before committing or rebasing.
- Distinctive: line 206
Stop on migration failure.
- Very specific: line 222
If {upstream_url} is none, skip this step and continue with Step 5.
- Very specific: line 226
If {in_worktree} is true, review the changes and continue the worktree update:
- Very specific: line 281
Run /pull logic (sync base branch, rebase working branch, pull memory).
“Common” is measured: kept by at least 6 in 10 of the 63 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Update local Egregore environment — sync framework from upstream and pull repos.
When to invoke
User says: "/update", "update Egregore", "sync the framework", "get the latest framework" — or framework behavior seems broken or missing (the first thing to try).
Not this: syncing managed repos + memory only, no framework sync → /pull
What to do
- Sync framework from upstream (egregore-labs/egregore)
- Run post-update migrations (
bin/post-update.sh) - Run
/pull(sync base branch + memory) - Show what changed
Step 1: Detect environment
Detect the base branch and whether we're in a worktree. Framework updates MUST land on the base branch, never on working branches.
bash bin/base-branch.shUse the printed branch name as {base}; quote placeholders in single quotes when you use them in a command, and write any single quote inside a value as '\''. A non-zero exit means the configuration could not be resolved: stop before any Git change.
git branch --show-currentUse the printed branch as {current_branch} for the non-worktree switch and restore steps.
# Detect worktree: .git is a file (not a directory) in worktrees
test -f .gitUse true as {in_worktree} if the test exits successfully; otherwise use false. If {in_worktree} is true, locate the main checkout:
git rev-parse --path-format=absolute --git-common-dirUse the printed common Git directory's parent as {main_dir}, the main checkout.
Step 2: Sync framework to base branch
Egregore is a framework — updates come from upstream, not from your own repo's history.
Freeze lever — check FIRST, before touching any remote:
bash bin/config-get.sh upstream_urlUse the printed value as {upstream_url}. If it prints none, this instance does not pull framework from
upstream — it is either the framework source of truth (framework changes are
authored here and flow OUT via /sync-public) or deliberately frozen. Skip
Step 2 entirely — do NOT add an upstream remote, do NOT checkout any path.
Tell the user: ⛔ upstream_url is "none" — this instance never pulls framework
from upstream. Skipping framework sync; running migrations + /pull only. Then
continue with Step 3. A wholesale upstream checkout on a source-of-truth
instance reverts downstream work (the 578deee incident: 23 files, −1131 lines).
In a worktree: The base branch is checked out in the main repo. Use git -C to update it there — git checkout '{base}' would fail since git won't let two worktrees share a branch.
Not in a worktree: Switch to the base branch directly.
Use {upstream_url} as {upstream} when set; if the command prints nothing, use
https://github.com/egregore-labs/egregore.git as {upstream}.
If {in_worktree} is true, ensure the upstream remote exists in the main checkout:
git -C '{main_dir}' remote add upstream '{upstream}'If it reports that the remote already exists, run git -C '{main_dir}' remote set-url upstream '{upstream}' instead.
git -C '{main_dir}' fetch upstream main --quietIf {in_worktree} is false, ensure the upstream remote exists in this checkout:
git remote add upstream '{upstream}'If it reports that the remote already exists, run git remote set-url upstream '{upstream}' instead.
git fetch upstream main --quietWorktree path
If {in_worktree} is true, sync framework paths only in the named main checkout:
bash bin/update-framework.sh --main-dir '{main_dir}'Stop if the command fails: the target checkout, upstream remote, and fetched
upstream/main must exist. Individual missing or failed paths are tolerated and
reported once. This path checkout is unaffected by the user's merge or rebase
settings; it never switches branches or discovers another worktree.
if [ '{in_worktree}' = "true" ]; then
# Regenerate AGENTS.md. It is GENERATED from CLAUDE.md by
# bin/codex-render-spec.mjs and is deliberately NOT in the overlay above —
# so without this step downstream workspaces never receive AGENTS.md framework
# changes (e.g. the Claude-Code runtime-precedence guard). Regenerate from the
# freshly-synced CLAUDE.md + script; fall back to the prebuilt upstream copy if
# node is unavailable or the render fails.
if command -v node >/dev/null 2>&1 && [ -f '{main_dir}/bin/codex-render-spec.mjs' ]; then
node '{main_dir}/bin/codex-render-spec.mjs' 2>/dev/null \
|| git -C '{main_dir}' checkout upstream/main -- AGENTS.md .codex/spec-manifest.json 2>/dev/null || true
[ -f '{main_dir}/bin/pi-render-spec.mjs' ] && node '{main_dir}/bin/pi-render-spec.mjs' 2>/dev/null || true
[ -f '{main_dir}/bin/prime-render-spec.mjs' ] && node '{main_dir}/bin/prime-render-spec.mjs' 2>/dev/null || true
else
git -C '{main_dir}' checkout upstream/main -- AGENTS.md .codex/spec-manifest.json 2>/dev/null || true
fi
# Regenerate Codex adapter skills from the freshly-synced Claude skills.
# Generated adapters carry a marker; hand-written natives are never touched.
# Without this, adapters for changed skills go stale until the next manual run.
[ -f '{main_dir}/bin/codex-sync-skills.sh' ] && (cd '{main_dir}' && bash bin/codex-sync-skills.sh) >/dev/null 2>&1 || true
# Restore org-owned skills (egregore.json → owned_skills[]) before committing.
# On a name collision the org's committed version wins; the script reports it.
(cd '{main_dir}' && bash bin/restore-owned-skills.sh) || true
fiNon-worktree path
If {in_worktree} is false, use false as {switched} initially.
Still only when {in_worktree} is false, if {current_branch} differs from
{base}, stash the work and switch to the base branch, recording the switch
for Step 4. If they match, keep the current branch and leave {switched} as false.
git stash --quiet 2>/dev/null || true
git checkout '{base}' --quiet 2>/dev/nullAfter switching successfully, use true as {switched} for Step 4.
If {in_worktree} is false, sync the same framework paths in this checkout:
bash bin/update-framework.shStop on failure as in the worktree path, then continue the non-worktree path:
if [ '{in_worktree}' = "false" ]; then
# Regenerate AGENTS.md from the freshly-synced CLAUDE.md (it is generated by
# bin/codex-render-spec.mjs and not in the overlay above). Fall back to the
# prebuilt upstream copy if node is unavailable or the render fails.
if [ -f bin/node-run.sh ] && [ -f bin/codex-render-spec.mjs ]; then
bash bin/node-run.sh bin/codex-render-spec.mjs 2>/dev/null \
|| git checkout upstream/main -- AGENTS.md .codex/spec-manifest.json 2>/dev/null || true
[ -f bin/pi-render-spec.mjs ] && bash bin/node-run.sh bin/pi-render-spec.mjs 2>/dev/null || true
[ -f bin/prime-render-spec.mjs ] && bash bin/node-run.sh bin/prime-render-spec.mjs 2>/dev/null || true
else
git checkout upstream/main -- AGENTS.md .codex/spec-manifest.json 2>/dev/null || true
fi
# Regenerate Codex adapter skills from the freshly-synced Claude skills
# (generated adapters carry a marker; hand-written natives are never touched).
[ -f bin/codex-sync-skills.sh ] && bash bin/codex-sync-skills.sh >/dev/null 2>&1 || true
# Restore org-owned skills (egregore.json → owned_skills[]) before committing.
# On a name collision the org's committed version wins; the script reports it.
bash bin/restore-owned-skills.sh || true
fiIf {in_worktree} is false, show the changes before continuing:
if [ '{in_worktree}' = "false" ]; then
# Show what changed
git diff --stat HEAD
fiFramework paths synced: bin/, egregore_runtime/, .claude/commands/, .claude/skills/, .claude/hooks/, .claude/context/, .claude/agents/, .pi/, .prime/, loom/, CLAUDE.md, skills/
Regenerated: AGENTS.md + .codex/spec-manifest.json via bin/codex-render-spec.mjs, .pi/APPEND_SYSTEM.md + .pi/spec-manifest.json via bin/pi-render-spec.mjs, .prime/agent/APPEND_SYSTEM.md + .prime/agent/spec-manifest.json via bin/prime-render-spec.mjs, then generated Codex adapter skills via bin/codex-sync-skills.sh, so all derived harnesses stay aligned with CLAUDE.md and the canonical skills.
Never touched: egregore.json, .env, memory/, .egregore-state.json, .mcp.json — except one migration: bin/post-update.sh rewrites a Connected api_url that still names the hosted API's retired October 2026 origin, and stages only that change for the update commit. It replaces only the address text, byte for byte, and keeps the file's mode and line endings. It leaves the file as is, with a warning, when it is a link, missing, unreadable, set aside by a sparse checkout, or Local in either the committed or the working copy, or when its api_url is escaped or repeated.
Org-owned skills: names in egregore.json → owned_skills[] are restored from the org's committed state after the overlay (bin/restore-owned-skills.sh) — upstream never overwrites them; collisions are reported instead.
Step 3: Post-update migrations
After syncing, run the updated bin/post-update.sh before committing or rebasing.
The first update through an older overlay can add the missing Runtime core here.
In worktrees, run in {main_dir} so migrations affect the main checkout.
Stop on migration failure; do not commit or rebase a partial update.
if [ '{in_worktree}' = "true" ]; then
if [ -f '{main_dir}/bin/post-update.sh' ]; then
(cd '{main_dir}' && bash bin/post-update.sh) || exit 1
fi
else
if [ -f bin/post-update.sh ]; then
bash bin/post-update.sh || exit 1
fi
fiStep 4: Commit and restore the working branch
If {upstream_url} is none, skip this step and continue with Step 5; no
framework overlay was applied. Otherwise, commit the overlay and migrations
together before the working branch receives the update.
If {in_worktree} is true, review the changes and continue the worktree update:
if [ '{in_worktree}' = "true" ]; then
# Show what changed
git -C '{main_dir}' diff --stat HEAD
# Commit on base branch in main repo (.codex/skills/ carries the
# regenerated adapters)
git -C '{main_dir}' add -A .claude/ .pi/ .prime/ bin/ loom/ CLAUDE.md skills/ AGENTS.md .codex/spec-manifest.json .codex/skills/ 2>/dev/null
# Older upstreams lack the Runtime core; a missing pathspec would abort the add.
[ ! -e '{main_dir}/egregore_runtime' ] || git -C '{main_dir}' add -A -- egregore_runtime/ 2>/dev/null
if ! git -C '{main_dir}' diff --cached --quiet 2>/dev/null; then
EGREGORE_FRAMEWORK_UPDATE=1 git -C '{main_dir}' commit -m "Update Egregore framework from upstream"
git -C '{main_dir}' push origin '{base}' --quiet 2>/dev/null || true
fi
# Rebase worktree branch onto updated base
git stash --quiet 2>/dev/null || true
git fetch origin '{base}' --quiet
if ! git rebase 'origin/{base}' --quiet 2>/dev/null; then
git rebase --abort 2>/dev/null || true
echo '⚠ Rebase had conflicts — aborted. Run: git rebase origin/{base} and resolve manually.'
fi
git stash pop --quiet 2>/dev/null || true
fiFor the non-worktree case:
if [ '{in_worktree}' = "false" ]; then
git add -A .claude/ .pi/ .prime/ bin/ loom/ CLAUDE.md skills/ AGENTS.md .codex/spec-manifest.json 2>/dev/null
[ ! -e egregore_runtime ] || git add -A -- egregore_runtime/ 2>/dev/null
if ! git diff --cached --quiet 2>/dev/null; then
EGREGORE_FRAMEWORK_UPDATE=1 git commit -m "Update Egregore framework from upstream"
git push origin '{base}' --quiet 2>/dev/null || true
fi
# Switch back to working branch, rebase, restore user's work
if [ '{switched}' = "true" ]; then
git checkout '{current_branch}' --quiet 2>/dev/null
if ! git rebase '{base}' --quiet 2>/dev/null; then
git rebase --abort 2>/dev/null || true
echo '⚠ Rebase had conflicts — aborted. Run: git rebase {base} and resolve manually.'
fi
git stash pop --quiet 2>/dev/null || true
fi
fiThe EGREGORE_FRAMEWORK_UPDATE=1 marker tells the branch guard this is safe on the base branch.
Step 5: Pull repos
Run /pull logic (sync base branch, rebase working branch, pull memory).
Example (on main, no worktree)
> /update
Syncing framework from upstream...
bin/activity-data.sh | 89 +++++------
.claude/skills/handoff/ | new
bin/post-update.sh | 12 +++---
3 files changed, 32 insertions(+), 22 deletions(-)
Running post-update migrations...
✓ Removed .claude/commands/ (migrated to skills)
✓ Framework updated and committed to main
Pulling...
main ✓ synced
memory ✓ up to dateExample (on working branch in worktree)
> /update
Syncing framework in main repo (on develop)...
bin/notify.sh | 12 +++---
.claude/skills/update/ | modified
2 files changed, 18 insertions(+), 6 deletions(-)
✓ Framework updated and committed to develop
✓ Rebased working branch onto develop
Pulling...
develop ✓ synced
memory ✓ up to dateIf framework is already current
Syncing framework from upstream...
✓ Already up to dateDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

