一键导入
sync
Synchronizes the git repo between machines mid-session. Commits local changes, pulls --rebase from origin, handles conflicts interactively, and pushes.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Synchronizes the git repo between machines mid-session. Commits local changes, pulls --rebase from origin, handles conflicts interactively, and pushes.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Switch the ACTIVE UNIVERSE of this brain, or create a new one (ADR 0034). A universe is a soft retrieval scope (e.g. successive employers, clients, spheres): when you work one universe, searches default to its notes plus your cross-cutting ones. Use when the user wants to switch / change / set the current universe / context / scope, list their universes, or create / add a new universe / context (e.g. 'switch to the acme universe', 'change de contexte', 'crée un univers Blue Team', 'in which universe am I?', 'liste mes univers'). This is invisible until a second universe exists. It does NOT touch notes and needs no reindex — it only re-points which universe is active.
Imports / migrates the notes from a PREVIOUS second brain (or any external vault) into THIS brain — recover, transport, bring over, re-home, transfer your old notes / anciennes notes from another folder. Use when the user wants to import / importer, migrate / migrer, transport / transporter, recover / récupérer, or bring in the content of an old / previous second brain — e.g. 'importe mes anciennes notes depuis <chemin>' or 'migrate my old brain'. Safe + opt-in: shows a plan, confirms, copies the vault content only, never overwrites, skips demo notes, then reindexes.
Importe / migre les notes d'un PRÉCÉDENT second cerveau (ou de n'importe quel vault externe) dans CE cerveau — récupérer, transporter, rapatrier, transférer tes anciennes notes depuis un autre dossier. À utiliser quand l'utilisateur veut importer, migrer, transporter, récupérer ou rapatrier le contenu d'un ancien / précédent second cerveau — p. ex. « importe mes anciennes notes depuis <chemin> » ou « migre mon ancien cerveau ». Sûr + opt-in : montre un plan, confirme, copie le contenu du vault uniquement, n'écrase jamais, ignore les notes de démo, puis réindexe.
Fan-out/fan-in architecture to pull in the DELTA of external sources (Slack, Google Drive / transcripts, Calendar, mail…) via parallel READ-ONLY sub-agents. Internal technical reference — it's the engine of Phase 2 of the main flow (question → sync sources in background) and of a possible morning briefing. Not a user command: it's your questions that trigger the pull.
Consolidate raw captures into durable entity/topic pages (Axis 1, Track C): review recent meetings / daily / transcripts and PROMOTE their substance into the higher-order wiki — create the page for a person mentioned but never filed, refresh a topic page a fresher note left behind, weave the backlinks. A deterministic scan surfaces WHAT needs consolidating; parallel read-only sub-agents draft each merge; you PROPOSE, the user confirms, and the write reuses the /file-back builder (never overwrites). Triggered by '/consolidate', 'consolidate my captures', 'promote my raw notes', 'update my entity pages', 'compile my wiki', 'consolide mes captures', 'mets à jour mes pages', 'promeus mes notes brutes'.
File a hard-won answer back into the vault as a durable note (Axis 1): after a substantive exchange, PROPOSE distilling it into a topic / decision / person / meeting page — with a suggested target zone, tags and [[links]] — then write it only once the user says yes. The write goes through a deterministic builder so the note is taxonomy-conformant by construction (never re-introduces the defects /lint reports). Triggered by '/file-back', 'file this back', 'save this answer', 'turn this into a note', 'garde cette réponse', 'classe ça dans mon cerveau', 'fais-en une note durable'.
| name | sync |
| description | Synchronizes the git repo between machines mid-session. Commits local changes, pulls --rebase from origin, handles conflicts interactively, and pushes. |
| version | 1.0.0 |
User command. Useful when working on several machines (personal / work laptop) and you want to pull in changes pushed from the other without leaving the session.
SessionStart hook (which pulls at startup) for mid-session cases.ℹ️ Requires a configured git remote (
origin). For purely local use, this skill is useless.
git status --porcelain
Clean → go to step 3. Dirty → step 2.
git add .
git commit -m "auto: vault/claude sync"
Creates a safe restore point before the rebase.
git fetch origin
git rebase origin/$(git branch --show-current)
Success → summary + step 5. Conflict → step 4.
git diff --name-only --diff-filter=UConflict on N file(s). Options:
- merge: I resolve and we continue the rebase
- abort:
git rebase --abort— back to the previous state (the local commit is safe)
git add the resolved files, git rebase --continue.git rebase --abort, report that the local commit is intact, stop.git push
Show: local commit yes/no, files pulled in from the other machine, push status.
git fetch fails → report, local changes intact.