Menu
Pull this repo's memhub DB from the Google Drive synced folder at session start and adopt newer cross-machine state with user approval.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Read-only health check of the memhub project in this repo — schema version, render freshness, write-log activity
Bootstrap memhub in this repo — initialize the SQLite store, seed starter state and architecture narratives, render PROJECT.md and PROJECT_LEDGER.md
Initialize memhub for a repo in OpenCode; use when the user asks to bootstrap project memory.
Summarize this memhub session, route updates into the database, then re-render PROJECT.md and PROJECT_LEDGER.md
Rebuild + install memhub and bring every memhub instance on this machine (each known repo DB + the machine-global store) to head schema, resync installed agent skill wrappers, with a one-time fix for the ~/.local/bin PATH shadow. Run from the memhub source repo.
Wrap up an OpenCode memhub session; run the binary-rendered policy, draft updates, get per-item approval, write, and render.
| name | catch-up |
| description | Pull this repo's memhub DB from the Google Drive synced folder at session start and adopt newer cross-machine state with user approval. |
| compatibility | opencode |
Bring this machine's memhub memory up to date with another machine. The transport is an OS-level synced folder (Google Drive for Desktop on macOS/Windows, rclone mount on Linux) mirrored to a local path; memhub stays offline and just reads/writes that path. Prefer the memhub.sync_* MCP tools — they default the Drive folder to the canonical <drive_subpath>/memhub/<project_id>, so you never build that path by hand; CLI is the fallback.
Workflow:
memhub.sync_status. If enabled is false, tell the user to run memhub sync enable and stop. If project_id_error is set (no git remote) or remote_dir_error is set (usually an empty drive_subpath), stop and ask the user to set it in .memhub/config.toml. Otherwise remote_dir is the resolved snapshot folder.memhub.sync_check (no args — it targets remote_dir). If project_id_mismatch is set or schema_blocks_adopt is true, stop and explain (the latter needs memhub upgrade first).no-remote, say "nothing to catch up yet" and stop (first-run, or mid-sync). On drive-ahead, recommend adopting; on diverged, warn that adopting discards local-only changes and require explicit approval; on up-to-date/local-ahead, do nothing.memhub.sync_adopt is gated by confirm: without confirm: true it returns the would-change verdict and changes nothing (a dry run). After approval call memhub.sync_adopt(confirm=true), then memhub.render, and report what changed.memhub sync status → memhub sync check → memhub sync adopt --yes → memhub render; each defaults to the canonical folder when the path is omitted.