agentleFS
benororbenoror/obsidianos_work/.agents/skills/sync-upstream-obsidianos/SKILL.md

sync-upstream-obsidianos

Skill166 starsChanged 5 months agoMITView on GitHub

Pull structural updates from upstream ObsidianOS into the local vault.

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
  1. Very specific:

    Verify upstream remote exists: git remote get-url upstream.

    line 22
  2. Distinctive:

    Verify working tree is clean (git status --short).

    line 26
  3. Very specific:

    Run .scripts/sync-upstream.sh --preview and show the output (new commits and changed files).

    line 30
  4. Distinctive:

    If there are no new commits, report "already up to date" and stop.

    line 32
  5. Very specific:

    If the user only asked for preview, stop here.

    line 34
  6. Distinctive:

    If the merge had conflicts, relay the conflict list and instruct the user to resolve manually.

    line 53
  7. Very specific:

    If the upstream remote doesn't exist, do not create it automatically — prompt the user for the URL.

    line 60

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Sync Upstream ObsidianOS

Shortcut to run .scripts/sync-upstream.sh.

Usage

CommandWhat it does
/sync-upstream-obsidianosPreview and merge upstream updates
/sync-upstream-obsidianos previewPreview only — show what's new without merging

Workflow

1. Check prerequisites

  • Verify upstream remote 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.sh

4. 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 .gitattributes merge=ours rules.
  • Files matching patterns in .sync-exclude are auto-removed from the merge (e.g. upstream example files).
  • This skill never pushes — the user decides when to push.
  • If the upstream remote doesn't exist, do not create it automatically — prompt the user for the URL.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.