From pce-memory-plugin
Team knowledge synchronization skill for pce-memory v2. Manages push/pull/status with memory_type-aware export/import and layer-aware sync rules. Triggered by: 'sync knowledge', 'push knowledge', 'pull team knowledge', 'check sync status'.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pce-memory-plugin:pce-syncThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Synchronize durable pce-memory knowledge across team members. v2 sync preserves `memory_type` and follows layer-aware export/import rules.
Synchronize durable pce-memory knowledge across team members. v2 sync preserves memory_type and follows layer-aware export/import rules.
Parse $ARGUMENTS:
push → Export local knowledgepull → Import team knowledgestatus → Check sync stateExport syncable durable knowledge to .pce-shared/.
pce_memory_sync_push()
$PCE_SYNC_TARGET_DIR (default: .pce-shared/)PCE_SYNC_AUTO_STAGE=true, auto git addPCE_SYNC_SCOPE_FILTERmemory_type is exported with each durable claimpromotion_queue is local review state and is never exportedImport team knowledge from .pce-shared/.
pce_memory_sync_pull()
// Or dry-run to preview
pce_memory_sync_pull({ dry_run: true })
public < internal < pii < secret (upgrade only)memory_type is preserved on import and backfilled onto existing claims only when the receiver is missing itpromotion_queue stays local-only because it represents review/rollback governance statepce_memory_sync_status()
Returns:
# Install hooks
./scripts/git-hooks/install-hooks.sh
# Set environment
export PCE_SYNC_ENABLED=true
git commit → pre-commit hook → sync push (auto export)
git pull → post-merge hook → sync pull (auto import)
See crdt-merge-guide.md.
pce_memory_state. Durable claims must exist before exportmemory_type, but does not overwrite an existing receiver value unless other merge rules applysync status, then sync push -> git commit -> git pushnpx claudepluginhub caphtech/pce-memory --plugin pce-memory-pluginManages a multi-layered knowledge system: save, organize, sync, deduplicate, and retrieve across local files, MCP memory, vector stores, and Git repos.
Manages multi-layer knowledge systems across local files, MCP memory, Git repos, and Supabase. Handles ingestion, deduplication, sync, and retrieval for persistent knowledge.
Syncs Zettelkasten memory cards across devices via git push/pull/merge. Initializes remotes with URL or auto-creates private GitHub repo via gh CLI. Use when backing up or sharing cards multi-device.