obsidian-sync-helperlisted

# Obsidian Sync Helper The Obsidian-as-context loop only works if `~/Brain/Projects/<name>.md` reflects what the project actually looks like in git. Drift kills the loop silently — the next session loads a stale note, makes a decision against an outdated picture, and the project diverges from its own documentation. This skill plugs the leak. It reads the project note, walks recent git history, and tells the operator where the two have drifted apart. Read-only by default — the operator owns the vault; the skill produces a candidate diff, never a silent edit. ## When to Use - The operator is in a project directory and asks to "verify the Obsidian note", "sync the brain", "check the project note", or any variant. - The skill is chained from `weekly-monday-review` when drift is detected during the Monday scan. - The operator just shipped something significant (a deploy, a feature, a deprecation) and wants a checkpoint before closing the session — the post-day update from `workflows/ship-a-product-in-a-day.md` block 7. - The operator returns to a project after a paused week and wants to re-establish what the note says vs what the repo actually contains. - ECC has no Obsidian skill in its 182-skill catalog. Adjacent skills (`knowledge-ops`, `project-flow-ops`) are generic project-state and do not know about the `~/Brain/Projects/<name>.md` convention; use this one specifically for the operator's vault loop. ## Inputs - The project name. Default: derive from the basename of th