sync-upstream-obsidianos
Skill166 starsChanged 5 months agoMITView on GitHub
Pull structural updates from upstream ObsidianOS into the local vault.
In this repository29 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .agents/skills/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/qmd-search.mdcCursor rule
- .cursor/rules/skill-conventions.mdcCursor rule
- .cursor/rules/skill-registry.mdcCursor rule
- cache-notesSkill
- commitSkill
- defuddleSkill
- fill-participantsSkill
- followup-todosSkill
- json-canvasSkill
- last-1on1Skill
- mail-transcriptsSkill
- meetingSkill
- migrate-tagsSkill
- note-statusSkill
- obsidian-basesSkill
- obsidian-cliSkill
- obsidian-markdownSkill
- onboard-personSkill
- organize-meetingsSkill
- otter-fetchSkill
- people-stubsSkill
- qmdSkill
- recapSkill
- sprint-retroSkill
- vault-healthSkill
- workspace-modeSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 3 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 22
Verify upstream remote exists: git remote get-url upstream.
- Distinctive: line 26
Verify working tree is clean (git status --short).
- Very specific: line 30
Run .scripts/sync-upstream.sh --preview and show the output (new commits and changed files).
- Distinctive: line 32
If there are no new commits, report "already up to date" and stop.
- Very specific: line 34
If the user only asked for preview, stop here.
- Distinctive: line 53
If the merge had conflicts, relay the conflict list and instruct the user to resolve manually.
- Very specific: line 60
If the upstream remote doesn't exist, do not create it automatically — prompt the user for the URL.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Sync Upstream ObsidianOS
Shortcut to run .scripts/sync-upstream.sh.
Usage
| Command | What it does |
/sync-upstream-obsidianos | Preview and merge upstream updates |
/sync-upstream-obsidianos preview | Preview only — show what's new without merging |
Workflow
1. Check prerequisites
- Verify
upstreamremote exists:git remote get-url upstream. If missing, tell the user to add it:git remote add upstream <url-to-upstream-repo> - Verify working tree is clean (
git status --short). If dirty, ask the user to commit or stash first.
2. Preview
Run .scripts/sync-upstream.sh --preview and show the output (new commits and changed files).
If there are no new commits, report "already up to date" and stop.
If the user only asked for preview, stop here.
3. Confirm and merge
Present the preview results and ask the user to confirm before merging.
On confirmation, run the full sync:
echo y | ./.scripts/sync-upstream.sh4. Report results
Show the merge outcome:
- Which files were updated.
- Whether any files were excluded via
.sync-exclude. - The final commit (
git log -1 --oneline).
If the merge had conflicts, relay the conflict list and instruct the user to resolve manually.
Important Notes
- The script protects personal files (Meetings, Teams, Templates, etc.) via
.gitattributesmerge=ours rules. - Files matching patterns in
.sync-excludeare auto-removed from the merge (e.g. upstream example files). - This skill never pushes — the user decides when to push.
- If the
upstreamremote doesn't exist, do not create it automatically — prompt the user for the URL.
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.

