agentleFS
RoberdanRoberdan/roberdan-os/skills/sync/skill.md

sync

Skill2 starsChanged 32 days agoMITView on GitHub

Keep Obsidian vault (durable memory) and in-repo docs aligned. Anti-drift. Read vault before asking. MANUAL — post-task-sync only regenerates the per-platform wrappers and is opt-in on RDA_AUTOSYNC=1.

54 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use develop, scope and 10 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.
  • hong9LeeSkill

    develop

    빌드, 아키텍처, git 관련 작업 시 OMS MSA 공통 인프라 규칙을 적용한다. 기술 스택, 빌드 명령, 헥사고날 아키텍처 구조, git 워크플로우, AI Context 동기화 규칙을 다룬다. 코드 작성 컨벤션은 /convention, 테스트 컨벤션은 /test-guide 스킬을 참조.

    Also in 6 projects that use this

  • YuriNachosSkill

    scope

    Configure claude-scope status line widgets for Claude Code. Use when user wants to customize widgets, change theme, reorder elements, or modify display style.

    Also in 7 projects that use this

  • nicolasestremSkill

    document

    Create focused documentation for specific components or features

    Also in 5 projects that use this

  • kt057Skill

    check

    lint, typecheck, test を一括実行して結果をサマリーする

    Also in 6 projects that use this

  • Microsoft AzureSkill

    test

    Also in 8 projects that use this

  • Microsoft AzureSkill

    validate

    Run the full CI validation workflow locally before submitting a PR. Use this as a final check to ensure all Azure DevOps CI pipeline steps will pass.

    Also in 4 projects that use this

The file

Files
skill.md

sync — align the vault and in-repo docs

Roberto keeps durable memory and engineering docs aligned. Drift between them is one of his top criticisms ("that plan got lost somewhere"). This skill reconciles them.

Sources of truth

SystemWhat it isSource of truth for
Obsidian Vault (~/Obsidian/Roberdan's Vault)durable memory, ~312 notesdecisions, people, history, masterplans
In-repo docsAGENTS.md, docs/plans/, ADRengineering truth of the code

Flow

  1. Read the vault BEFORE asking — gbrain search "<context>" --source vault (semantic). The answer is probably already there.
  2. Reconcile — if they diverge, identify the authoritative source for that type of information (table above) and propagate.
  3. Update the masterplan on the vault without Roberto needing to ask.
  4. Update in-repo docs (AGENTS.md, repo plan, ADR) if an interface/decision changed.

When

At the end of every phase of a long task (not just at the end), reconcile manually. hooks/post-task-sync.sh only regenerates wrappers (opt-in RDA_AUTOSYNC=1); it does not reconcile the vault or engineering docs.

Guardrail

  • Vault is git-backed with AutoGit: only one agent at a time writes to the vault (lock .git/index.lock).
  • Deleting notes/sources = human gate #4 (non-regenerable data) — never automatic.

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.