sync-repos
Skill293 starsChanged 11 days agoMITView on GitHub
Smart sync of all Egregore repos (memory + managed repos + current repo) — fetches first, only pulls if behind. Use for /sync-repos or 'sync all repos'.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- codemonkey85/PKMDS-Blazortheir own version, first seen Oct 8, 2026
- ridermw/my-skillstheir own version, first seen Sep 10, 2026
- SmartAssets-io/skillstheir own version, first seen Aug 12, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- codemonkey85/PKMDS-Blazor★ 241same name
- SmartAssets-io/skills★ 2same name
- ridermw/my-skills★ 0same name
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
- telegram-connectSkill
- telemetrySkill
- testSkill
- the-spiralSkill
- tui-designSkill
- tutorialSkill
- updateSkill
- viewSkill
- visual-explainSkill
- wrapSkill
- preview-designSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 1 is distinctive, and 5 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 48
Use the printed revisions as {local_sha} and {remote_sha}.
- Very specific: line 57
Use the printed count as {behind} for the output.
- Very specific: line 67
Use the printed value as {branch}.
- Very specific: line 73
If the rebase fails, run git rebase --abort, then git merge develop -m 'Sync with develop'.
- Distinctive: line 87
Use absolute paths with git -C to avoid permission prompts.
- Very specific: line 102
Use git -C /absolute/path — no cd commands
“Common” is measured: kept by at least 6 in 10 of the 3 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
Smart sync of all Egregore repos. Fetches first, only pulls if behind.
When to invoke
User says: "/sync-repos", "sync all repos", "sync everything", "get every repo up to date"
Execution boundary
This is deterministic multi-repository sync. Run it inline with bounded parallel fetches; do not spend a Loom/model-routing call or delegate it to another agent.
Repos to sync
../{memory_dir}— shared knowledge (derived frommemory_repoinegregore.json)- Any repos listed in the
reposarray inegregore.json(as sibling directories../{repo}) - Current repo (egregore-core)
Read egregore.json first to get the dynamic list:
# Memory repo directory
bash bin/config-get.sh memory_dir
# Managed repos
bash bin/config-get.sh reposUse the first command’s printed value as {memory_dir} and each line from the second as a managed {repo} name; for each value, quote it in single quotes when you use it in a command, and write any single quote inside the value as '\''. If a command prints nothing, it contributes no repo to sync.
Execution
For each repo, run these commands:
# 1. Fetch (always)
git -C /path/to/repo fetch origin --quiet
# 2. Compare local vs remote
git -C /path/to/repo rev-parse HEAD
git -C /path/to/repo rev-parse origin/mainUse the printed revisions as {local_sha} and {remote_sha}. If they differ, pull and then count commits behind:
# 3. Only pull if different
git -C /path/to/repo pull origin main --quiet
# Count commits behind
git -C /path/to/repo rev-list HEAD..origin/main --countUse the printed count as {behind} for the output. If the revisions match, report the repo as up to date and skip the pull and count.
For the current repo (egregore-core): sync the develop branch instead of main:
# Update local develop ref without switching branches (safe for concurrent sessions)
git fetch origin develop:develop --quiet
# If on dev/* branch, rebase onto develop
git branch --show-currentUse the printed value as {branch}. If it starts with dev/, rebase onto develop:
git rebase develop --quietIf the rebase fails, run git rebase --abort, then
git merge develop -m 'Sync with develop'. Continue to the merge only if the
abort succeeds:
git rebase --abortgit merge develop -m 'Sync with develop'For any other branch, skip the rebase and merge.
Use absolute paths with git -C to avoid permission prompts.
Output format
Syncing Egregore repos...
{memory-dir} ↓ 3 commits → pulled
{repo-1} ✓ up to date
{repo-2} ✓ up to date
egregore-core ↓ 1 commit → pulledRules
- Use
git -C /absolute/path— nocdcommands - Fetch ALL repos first (parallel if possible), then compare/pull
- Show commit count when pulling
- Skip repos that don't exist (no error)
Does 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.

