crm-synclisted

Sync CRM knowledge notes in a vault with the live CRM code repositories: pull the read-only repos, detect which changed, and refresh only the affected reverse-engineering notes and the keep/drop/decide note. Triggers: "/crm-sync", "refresh CRM knowledge", "what changed in the CRM code".
tonydzi/second-brain-starter-kit · ★ 6 · AI & Automation · score 78

Install: claude install-skill tonydzi/second-brain-starter-kit

# /crm-sync - keep the CRM knowledge layer fresh The CRM (CHARM) is Anton's proven engine on GitLab. We reverse-engineered it once (2026-06-19) into a linked vault layer so his digital twin can `/ask` how the CRM works. Code keeps changing; this skill stops that knowledge from going stale silently. It is the recurring half of the standing rule `evaluate-recurring-into-routine`. **What this is NOT:** not a re-decompose-from-scratch. It is a DIFF-DRIVEN refresh: pull, see what changed, update only the notes that map to the changed code. ## Where everything lives - **Code (read-only clone, 16 repos):** `<CRM_REPOS_ROOT>` (memory `crm-gitlab`). - **Decomposition audit (HTML, source of the notes):** `<CRM_REPOS_ROOT>\_AUDIT\` (`Functional-Map.html`, `Know-How-Decomposition.html`, `Architecture-Deep.html`). - **Vault knowledge layer:** `$OBSIDIAN_VAULT/05-Resources/CRM-Engine/` - `_CHARM-CRM-Engine-MOC.md` (hub) - `crm-architecture-4-layers.md` - `crm-mtproto-engine.md` - `crm-core-autopilot.md` - `crm-admin-panel-api-brain.md` - `crm-data-model-mongo.md` - `crm-know-how-13-patterns.md` - `crm-landing-api-money.md` - decision: `$OBSIDIAN_VAULT/02-Decisions/decision-crm-keep-cc-drop-decide.md` ## Repo -> note map (which note to refresh when which code changes) | Code area in <CRM_REPOS_ROOT> | Note(s) to refresh | |---|---| | `admin-panel` / `admin-panel-api` (FastAPI brain, filter-DSL, $facet) | `crm-admin-panel-api-brain` | | `mtproto-api` (Telethon hands,