From okf-memory
Fold recent changes into the .knowledge/ concepts and restamp them
How this command is triggered — by the user, by Claude, or both
Slash command
/okf-memory:okf-syncThe summary Claude sees in its command listing — used to decide when to auto-load this command
Reconcile the OKF memory bundle with recent work, so it reflects current truth. Load the `okf-memory` skill and read its `references/maintenance.md` first. ## Procedure 1. **Confirm the bundle exists.** If there's no `.knowledge/index.md`, tell the user to run `/okf-init`. 2. **Find what changed.** Compare recent work against the bundle: - If a changed-file list was handed to you (the Stop hook names the files, or `.knowledge/.okf-dirty` lists them), target ONLY those files - this is the cheap path; do not re-scan the bundle. - Otherwise: `git log` / `git diff` since around the ol...
Reconcile the OKF memory bundle with recent work, so it reflects current truth.
Load the okf-memory skill and read its references/maintenance.md first.
Confirm the bundle exists. If there's no .knowledge/index.md, tell the user to run /okf-init.
Find what changed. Compare recent work against the bundle:
.knowledge/.okf-dirty lists them), target ONLY those files - this is the cheap path; do not re-scan the bundle.git log / git diff since around the oldest concept timestamp, plus whatever was edited this session.
Map changed paths to subsystems (which arch-*.md each touches).For each affected concept, run the after-a-change loop (from maintenance.md):
references/format.md (~150 words) - rewrite, don't accrete.timestamp to now.index.md if it changed.log.md.
Create a new concept file if a real subsystem now has none.Reconcile index.md - every concept line current, open-threads section updated.
Report which concepts were updated and which log.md lines were added. Don't claim a concept is fresh unless you actually re-grounded it against current code.
npx claudepluginhub fx818/okf-memory --plugin okf-memory